-->
Silent Install Switches For Msi X
The executable program that interprets packages and installs products is Msiexec.exe.
Note
Silent or Unattended Installation. Jump to bottom. It is possible to install Git for Windows silently using the following flags when called from a command-line prompt. And by inspecting the install.iss file (for custom options added only to Git for Windows' installer). Build a Silent MSI Package for Remote Installation Over a Network. EMCO MSI Package Builder is a tool for a silent creation of MSI packages. It allows you to generate MSI packages that can be installed in a non-interactive mode and are ready for unattended installation over a network. You should be able to use the /quiet or /qn options with msiexec to perform a silent install. MSI packages export public properties, which you can set with the PROPERTY=value syntax on the end of the msiexec parameters. For example, this command installs a package with no UI and no reboot, with a log and two properties. Msiexec /i testdb.msi INSTALLLEVEL=3 /l. msi.log COMPANYNAME='Acme 'Widgets' and 'Gizmos.' ' The following example shows advertisement options. Note that switches are not case-sensitive. Msiexec /JM msisample.msi /T transform.mst /LIME logfile.txt. The following example shows you how to install a new instance of a product to be advertised.
Karen marie moning read online. Msiexec also sets an error level on return that corresponds to System Error Codes.
The following table identifies the standard command-line options for this program. Command-line options are case insensitive.
Windows Installer 2.0: The command-line options that are identified in this topic are available beginning with Windows Installer 3.0. The Windows Installer Command-Line Options are available with Windows Installer 3.0 and earlier versions.
Option | Parameters | Meaning |
---|---|---|
/help | Help and quick reference option. Displays the correct usage of the setup command including a list of all switches and behavior. The description of usage can be displayed in the user interface. Incorrect use of any option invokes this help option. Example: msiexec /help [!Note] | |
/quiet | Quiet display option. The installer runs an installation without displaying a user interface. No prompts, messages, or dialog boxes are displayed to the user. The user cannot cancel the installation. Use the /norestart or /forcerestart standard command-line options to control reboots. If no reboot options are specified, the installer restarts the computer whenever necessary without displaying any prompt or warning to the user. Examples: msiexec /package Application.msi /quiet Msiexec /uninstall Application.msi /quiet Msiexec /update msipatch.msp /quiet Msiexec /uninstall msipatch.msp /package Application.msi / quiet [!Note] | |
/passive | Passive display option. The installer displays a progress bar to the user that indicates that an installation is in progress but no prompts or error messages are displayed to the user. The user cannot cancel the installation. Use the /norestart or /forcerestart standard command-line options to control reboots. If no reboot option is specified, the installer restarts the computer whenever necessary without displaying any prompt or warning to the user. Example: msiexec /package Application.msi /passive [!Note] | |
/norestart | Never restart option. The installer never restarts the computer after the installation. Example: msiexec /package Application.msi /norestart [!Note] | |
/forcerestart | Always restart option. The installer always restarts the computer after every installation. Example: msiexec /package Application.msi /forcerestart [!Note] | |
/promptrestart | Prompt before restarting option. Displays a message that a restart is required to complete the installation and asks the user whether to restart the system now. This option cannot be used together with the /quiet option.[!Note] | |
/uninstall | Uninstall product option. Uninstalls a product.[!Note] | |
/uninstall | /package This question - detect msi parameters for unattended install - is similar, but the links in the answer are broken and I can't figure out from the answer what I would do. Thanks. Community♦ ChadChad2,04744 gold badges2323 silver badges3737 bronze badges Silent Install Switch For Msi3 AnswersIf it's MSI, then the parameters are standard, you can get the list of options with msiexec /? or view the docs on MSDN.There's no way to detect options for an arbitrary EXE which options it supports, if any. Try to find docs from the vendor, or try Alexey IvanovAlexey Ivanov/? switch…10.2k44 gold badges3333 silver badges5555 bronze badges Just run through the installer with logging turned on and it will show you all of the possible parameters that the specific MSI accepts. For example: msiexec /log logfile.txt /i installer.msi Run through the entire installer and the logfile.txt will show you the passable parameters as 'Property(S)' or 'Property(C)' with the name in all caps. Source:http://www.codeproject.com/Articles/16767/How-to-Pass-Command-Line-Arguments-to-MSI-Installe matt wilkie6,7821919 gold badges6060 silver badges8989 bronze badges Jon HeeseJon Heese (Note: I posted a variation of this response on the detect msi parameters for unattended install question you mentioned.) There's lessmsi, is a great tool that certainly works here if you're willing to use a GUI and do some manual investigation. Disney sing it wii song list. You can try the following command: ..But it's unlikely that the above will have everything you're looking for. One way to essentially guarantee that you get all the possible properties is to actually perform either an installation, repair, or uninstall with the MSI file and log the process as mentioned in Jon Heese's answer. If you want less text to sift through in the log file, you can set the log setting to log only the properties: or I prefer a method that bypasses the need of install/remove/repair-ing through 'extraction'. The advantages this method has over lessmsi is that it doesn't require a 3rd-party utility (i.e. lessmsi), and it doesn't require you to mess with any installations. You do need to have enough disk space to actually install the program (and probably some additional space, to be safe). Then you can do something like: ![]() Note that the <absolute_path_to_extract_to> can point to a nonexistent directory (the command will create the directories necessary or fail).If you hate the installation UI for whatever reason you can append the /qr option, which will 'reduce' and possibly eliminate the UI without impairing the property logging process. Be warned however--if you go 'lower' than the reduced UI (viz. /qb |/passive or /qn |/quiet ), your <msi_property_logfile> may be missing some properties.The following command can effectively produce a Property log file for each MSI file in some directory (use DIR /B rather than DIR /B/S to not recurse subdirectories; remove the RD command if you want to keep the extracted files):and if you want to run that in PowerShell for whatever reason, use the command below instead: Once the process has finished, you simply open up the logfile and note the lines beginning with Property(S): /Property(C): as Jon Heese mentioned.Generally speaking, the parameters/properties that can be set for an install are logged in ALL CAPS; for example, ALLUSERS can be set ALLUSERS=1 so that the installation is for all users.YenForYangYenForYang Not the answer you're looking for? Browse other questions tagged windows-installerexeunattended-processing or ask your own question.
|