Msiexec /i 'client component pack.msi' /qn enterpriseipaddress=10.1.1.1 employeeportal=false ignite=true management=false networkmonitor=true realtime=true reporting=true salesforce=true scheduling=false softphone=true teleworker=false yse =false.
The Windows Installer technology uses Msiexec.exe for installing MSI and MSP packages. This tool gives you full control over the installation process, allowing you to set:
- install options (install, uninstall, administrative install, advertise a product)
- display options (full, basic or no UI during the installation)
- restart options (if the machine will be restarted after the installation)
- update options (apply or remove updates)
- repair options (only for an installed package)
- public properties which are used by the installation
The usual form of the msiexec command line is this:
Install Options
When launching an installation package, you can set the install type through these options:
- /i - normal installation
- /a - administrative install
- /j - advertise the product
- u - advertise to the current user
- m - advertise to all users
- /g - the language identifier used by the advertised package
- /t - apply transform to advertise package
- /x - uninstall the package
Sample command line:
Display Options
The user interface level of the installation can be configured according to the target environment. For example, a package distributed to clients should have a full UI, while a package deployed through Group Policy should have no user interface. Msiexec.exe sets the UI level of the installation through these options:
- /quiet - quiet mode (there is no user interaction)
- /passive - unattended mode (the installation shows only a progress bar)
- /q - set the UI level:
- n - no UI
- n+ - no UI except for a modal dialog box displayed at the end.
- b - basic UI
- b+ - basic UI with a modal dialog box displayed at the end. The modal box is not displayed if the user cancels the installation. Use qb+! or qb!+ to hide the button.
- b- - basic UI with no modal dialog boxes. Please note that /qb+- is not a supported UI level. Use qb-! or qb!- to hide the button.
- r - reduced UI
- f - full UI
Sample command line:
Restart Options
Sometimes an installation overwrites files which are in use or needs to reboot the machine in order to finish it. The reboot policy used by the installation can be set through these options:
- /norestart - the machine will not be restarted after the installation is complete
- /promptrestart - the user will be prompted if a reboot is required
- /forcerestart - the machine will be restarted after the installation is complete
Sample command line:
Logging Options
When debugging an installation package you can use multiple logging parameters in order to create a log. This log will contain different information for each parameter you use:
- /L - enable logging
- i - include status messages
- w - include non-fatal warnings
- e - include all error messages
- a - mention when an action is started
- r - include action-specific records
- u - include user requests
- c - include the initial UI parameters
- m - include out-of-memory or fatal exit information
- o - include out-of-disk-space messages
- p - include terminal properties
- v - verbose output
- x - include extra debugging information
- + - append to an existing log file
- ! - flush each line to the log
- * - log all information, except for v and x options
- /log - the equivalent of /l*
Sample command line:
Update Options
The Windows Installer command line can apply or remove updates (patches for example) through these options:
- /p - install an MSP patch. When installing a patch silently, you need to set REINSTALLMODE property to 'ecmus' and REINSTALL to 'ALL'. Otherwise the patch will simply update the MSI cached on the target machine.
- /update - apply updates (if there are multiple updates, you can separate them through the ';' character).
- /uninstall - remove an update for a product (if there are multiple updates, you can separate them through the ';' character)
- /package - specifies the package for which the update is removed.
Sample command lines:
In the above command line the first GUID is the Patch identifier GUID and the second one is the Product Code of the MSI for which the patch was applied.
Repair Options
If you have an installed package, you can use the Windows Installer command line for repairing it:
- /f - repair a package
- p - repair only if a file is missing
- o - repair if a file is missing or an older version is installed
- e - repair if file is missing or an equal or older version is installed
- d - repair if a file is missing or a different version is installed
- c - repair if a file is missing or the checksum does not match the calculated value
- a - forces all files to be reinstalled
- u - repair all the required user-specific registry entries
- m - repair all the required computer-specific registry entries
- s - repair all existing shortcuts
- v - run from source and recache the local package
Sample command line:
In the above command line the GUID is the Product Code of the MSI which will be repaired.
Set public properties
The name of a public property contains only uppercase letters (for example PROPERTY). This type of properties can be set through the command line like this: PROPERTY='value'.
Sample command line:
AdminStudio 11.5 | Repackager
Edition: This feature is available in AdminStudio Standard, Professional, and Enterprise Editions.
You can simultaneously build an InstallShield Editor project (.ism) and a Windows Installer package (.msi) from your Repackager project (.irp). However, before you do so, you must configure options in your Repackager project necessary for the build.
Note: For information on building a virtual application, see Automatically Generating a Virtual Application During Repackager Project Build.
To build an InstallShield Editor project (.ism) and a Windows Installer package (.msi):
1. | In the Repackager interface, open the Repackager project that you want to convert to an InstallShield Editor project and build a Windows Installer package. |
2. | Select Repackaged Output from the View List. The Repackaged Output view opens. |
3. | In the Editor Project field, enter the name and location of the InstallShield Editor Project file you want to create. |
4. | Select the Create a Windows Installer package (.msi) after creating the Editor project option, and select the following additional options: |
a. | The compression option that you select for this package depends upon the size of your application’s installation and your delivery method. |
Neither Setup.exe nor your .msi file can be spanned across multiple disks. So, if the source files associated with your Windows Installer package cannot fit on the same disk as the setup.exe and .msi file, you will need to include them in .cab files on other disks. But if you are performing a network installation and have unlimited space, there is no need to compress files or include additional files in .cab files.
From the list, select one of the following options:
Option | Description | ||||
Create single compressed .msi file | Select this option if you want to compress all necessary files inside the .msi package, as opposed to storing them outside of the .msi database. | ||||
Create single compressed setup.exe file | Select this option if you want to compress all files inside a setup.exe file, including the .msi file and all other necessary files. | ||||
Create .msi file + external compressed .cab file | Select this option if you want to create an .msi file and want to compress the rest of the necessary files in an external .cab file. For example, you might have an installation that contains three features—each containing a 1.5 MB file, Setup.exe, and the installation files for Windows NT—and you want to create a custom media type that is 2 MB in size. The build will span multiple disks.
| ||||
Create .msi file + external compressed .cab file + setup.exe | Select this option if you want to create an .msi file and a setup.exe file, and want to compress all the rest of the necessary files in an external .cab file. | ||||
Create uncompressed .msi file | Select this option if you want to create an uncompressed .msi file. All of the rest of the necessary files, in uncompressed format, would be shipped with the .msi file. | ||||
Create uncompressed .msi file and setup.exe | Select this option if you want to create an uncompressed .msi file along with a setup.exe file. All of the rest of the necessary files, in uncompressed format, would be shipped with the .msi and setup.exe files. |
b. | To reduce versioning conflicts by modifying an application so it always loads the versions of components—such as DLLs—with which it was originally developed and tested, select the Create an isolated version of the Windows Installer package. An additional Windows Installer package will be created in the same directory as the .ism file and the other .msi file, with the naming convention of: |
appname.isolated.msi
For more information on how Repackager isolates applications and the available isolation options, see Isolating Windows Installer Packages.
c. | Select the Run automated tests against the Windows installer package option to automatically run best practice tests against the newly built Windows Installer package to determine if it is built according to Windows Installer standards, and if it is in compliance with the installation requirements of the Windows operating system. |
d. | To build a virtual application, select the Create a Microsoft App-V application, Create a VMware ThinApp application, and/or Create a Citrix XenApp profile option. See Automatically Generating a Virtual Application During Repackager Project Build. |
Note: In order to select one of these virtualization options, you must have already selected the Create a Windows Installer package (.msi) after creating the Editor project option.
5. | A project template contains all of the default settings and design elements that you want to use as a starting point when you create an installation project. In the Repackaged Output Options area, select the InstallShield Editor Project Template you want to use when creating the project: |
• | Use the default Editor template—Select this option to use the default InstallShield Editor Project Template. |
• | Use a customized template—Select this option to use a customized InstallShield Editor Project Template. |
For example, if you wanted all of your InstallShield Editor projects to have a special custom dialog, a set of required redistributables, and a particular SQL script, you could create a project template that has all of those settings. Then, any time that you wanted to create a new project, you could base it off of your custom template. This enables you to avoid re-creating the custom dialog, re-adding the redistributables, and re-adding the SQL script every time that you create a new InstallShield Editor Project.
6. | Select Package Information from the View List. The Package Information view opens, where you can specify information for the Windows Installer package that you build from the Repackager project. Much of this information may be prepopulated based on settings used in the Repackaging Wizard. |
7. | Enter the following information: |
a. | Company Name—The name of the company that developed the product you are repackaging. |
b. | Product Name—The name of the product you are repackaging. |
c. | Version—The product’s version number. |
d. | Product URL—The URL for product information. This appears in Add/Remove Programs in the Control Panel. |
e. | Support URL—A URL for support information. This also appears in Add/Remove Programs in the Control Panel, and is often changed during repackaging to provide an internal support URL. |
8. | Select Advanced Settings from the View List. The Advanced Package Settings view opens. |
9. | Select the options that you want to use, as described in Configuring Advanced Conversion Options. |
10. | Select Repackaged Output on the View List. The Repackaged Output view opens. |
11. | Click the Build button. The build process begins, and its progress is reported in the output window. |
When the build process is complete, a Conversion completed message appears in the output window, a link to the build log file is provided, and the location of the .msi file is listed. For example:
Output file: C:1516261WinZip.msi
AdminStudio 11.5 Help LibraryJuly 9, 2012 | Copyright Information | Contact Us |