msiexec

With BAT/CMD script I can simply use "msiexec /i <whatever.msi> /quiet /norestart" and then check %errorlevel% for the result. With VBScript , using the Wscript.Shell object Run() method, I can get the result like this: "result = oShell.Run("msiexec /i ...", 1, True)" How can I do this with PowerShell? I would wrap that up in Start-Process and use the ExitCode property of the resulting process object. For example (Start-Process -FilePath "msiexec.exe" -ArgumentList "<<whatever>>" -Wait -Passthru).ExitCode $LastExitCode or $? depending on what you're after. The former is an integer, the latter

I want to push MSI installer with parameter using SCCM server. i.e. msiexec.exe /i "setup.msi" INSTALLFOLDER="SpecifiedInstallationLocation" CONFIGFILE="FileName" Can I use parameter name defined by me or I have to use specific parameter name in command line? Is any specific format to pass parameter? Can I able to pass parameter to MSI installer? If I use same command in batch file then it will works properly. Stein Åsmul In general questions about SCCM or corporate deployment tools may be better answered on the StackExchange system administrator site serverfault.com . Deployment is a crucial

Good afternoon, I need some help from some Microsoft gurus that deal with windows installer? I am trying to monitor msiexec utilising the debug keys within windows on a virtual machine and trying to fully understand how Msiexec is fully parsing command lines. I have set up the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\msiexec.exe Redirected into a sample application to monitor command line parsed. I have come across numerous examples from removing applications and installing for example C++ redistributable's. I understand the standard normal

I'm trying to uninstall an older version of our product which was installed using a WiX-built installer and after uninstalling it silently: msiexec /x{GUID} the program still appears in Control Panel. I've opened a separate item to explore that mystery, but another curious issue has popped up. I noticed that after running the install for this program, two entries (GUIDs) are added to HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall. One with the product GUID and one that I have no idea where it comes from. I've searched through the .msi and it's not in there. Both are

What are the Python 3 os commands to establish "writable data files and C-Drive paths" for a typical Windows 10 Application. There are several parts to this question: My Python 3 program creates (multiple) data files as part of it's purpose. When my MSI installer installs into /Programs, my Python executable does not have permission to create and write data files. Thus, the first part of my question is: Do I need to change my Python 3 program to create data files in a specific directory (using the os capabilities) and could you give me an example. The second part of my question is simply: What

Having an issue with WIX installer upgrade. Previously we had 2 version of installers 1 for per-machine and another for per-user. Currently we have developed a dual mode MSI. The dual mode MSI upgrades the PerUser version (on PC 1) of previous installer when install for yourself option is selected but when install for all (on PC 2 ) is selected it install a new product Is it some wrong that we are doing or is have to set some properties. We are using WIX. Please help If you had two setups before, it might be that you have two upgrade code and need to deal with both for the upgrade to work in