MSI
From the MSI section, it is possible to control how the installation is done, specify options, transforms, and define behavior if started on a terminal server. The settings displayed will depend on the template (Windows Installer and Windows Installer patch)
| MSI Section | Description |
| File name | Specify the MSI filename. Use the browse button to locate the file. With the Windows Installer patch template, specify the MSP file |
| Options | Specify the MSI options. The options for an msi file can typically be displayed using the Microsoft orca tool. Options should be delimited using (space). The default is REBOOT=REALLYSUPPRESS ALLUSERS=2, and REINSTALL=ALL for the Windows Installer patch template. The value can’t contain two double quotes in a row ("") |
| TS Options | Specify the MSI options for the program/script if it is executed on a terminal server. If you leave it empty, the value from Options is used. The default is REBOOT=REALLYSUPPRESS ALLUSERS=2. Only shown in the advanced view |
| TransformFile | Specify the transform file (.mst). The transform file typically handles changes to the install behavior. Transform files can be made using orca, Wise installer, Installshield, etc. The transform file must be in the same folder as the MSI file. Only shown in the advanced view |
| Log | The MSI setup is typically able to generate an extensive log that contains detailed information about file copy, registry manipulation, etc. It is highly recommended to generate the log if possible. Select one of the following options: Yes: Generate MSI log. This is the default No: Discard the MSI log The generated log will be located in the Msilogs subfolder of the CapaInstaller agent log folder on the client. The log file can grow to several megabytes. Only shown in the advanced view |
| TS TransformFile | Specify the transform file for the program/script if it is executed on a terminal server. If you leave it empty, the value from TransformFile is used. Only shown in the advanced view |
| Reinstall | This option defines how reinstallation requests should be handled. In this case, reinstallation means that the script/program is rerun. Select one of the following: ReInstall: Uninstall and then reinstall the application. Repair: Repair the existing installation. This is the default. Only shown in the advanced view. |
| Uninstall Guids | Use this value to specify any applications that must be uninstalled before installing the actual package. Separate the GUIDs with |. Use the browse button to locate GUIDs directly from a msi file. |
| Upgrade Guids | Windows Installer patch template only. Specify the GUIDs for which an MSI-patch package is able to upgrade. If the application isn’t installed (guid does not exist) the script/program will complete without patching anything. Enter one or more GUIDs for the application to be upgraded, separated with |. Click on the Browse link to select GUIDs from a list. |