The MSI tab is available only on Application objects created for MSI applications installed by Microsoft Windows Installer.
The MSI tab includes the following pages to help you configure and manage the distribution of MSI applications installed through the Microsoft Windows Installer:
The Properties property page, shown below, lets you override the public property values contained in the MSI package and add new public properties.
The MSI package contains the property values that were defined during the administrative installation of the application. These property values determine the way the Microsoft Windows Installer installs the application to the user's workstation. In some cases, you might want to change one or more of the property values. For example, a property value might define the default location for a user's work files. By adding the property to the Properties list and changing the property's value, you can override the default location defined in the MSI package.
If necessary, you can add public properties that were not included in the MSI package. When doing so, you should be careful to add only those properties that are valid for the package.
To override a property value, you change the property value and add the property to the Properties list so that Application Launcher knows to use that property value rather than the one defined in the MSI package. To do so, click Add to display the Select Property to Add dialog box. In the Value Name field, select the property whose value you want to override > enter the new value in the Value Data field > click OK to add the property to the Properties list.
To define a new property that is not already included in the MSI package, click Add to display the Select Property to Add dialog box. In the Value Name field, enter the new property's name > enter the property's value in the Value Data field > click OK to add the property to the Properties list.
For a list of properties and descriptions, see the Microsoft Developer Network (MSDN).
The Transforms property page, shown below, lists the transforms that Microsoft Windows Installer will apply to the MSI package during distribution. A transform adds, deletes, or changes properties in the MSI package to enable customizing of the installation for different groups of users.
Transforms are applied in the order they appear in the Transform List. If two transforms modify the same package property, the property retains the value applied by the last transform.
For information about creating transforms for your .MSI package, see the documentation you received with the software application.
Click Add > browse to and select the transform file (.mst file) you want added to the Transform List > click OK to add it to the list. If the transform file is in the same location as the .msi package, you can simply enter the filename in the Transform Path field.
IMPORTANT: The Windows Installer requires direct file access to MSI packages and transform files in order to open them. If a workstation does not have a network client that provides access to the MSI application and transform file (for example, the workstation is using the ZfD Management Agent only), you must force cache the MSI application to the workstation so that the Windows Installer can distribute it from the workstation's cache. You enable the Force Cache option on the Associations page.
If you force cache the application (because either the workstation is using the Management Agent only or you simply want the files available for installation and verification while in disconnected mode) , its transform files must be located in the same directory as the .msi file in order to be cached. When specifying the transform filename in the Transform Path field, you must enter the filename only (not the full path).
The Verify property page, shown below, determines the actions that Microsoft Windows Installer will take when instructed to verify (fix) the application.
When a user verifies the MSI application, Application Launcher launches Windows Installer. If no options are selected, Windows Installer will perform a full verification, which results in all files, settings, and so forth being reinstalled. If one or more options are selected, Windows Installer only performs the actions specified by the selected options.
Instructs Windows Installer to reinstall a file only if it is missing.
Instructs Windows Installer to reinstall a file if it is missing or if the installed file's version is older than the file in the MSI package.
Instructs Windows Installer to reinstall a file if it is missing or if the installed file's version is the same as or older than the file in the MSI package.
Instructs Windows Installer to reinstall a file if it is missing or if the installed file's version is not exactly the same as the file in the MSI package.
Instructs Windows Installer to perform a checksum on all executable files and to reinstall a file if it is missing or if the checksum verifies that the file is corrupt. Only files that have msidbFileAttributesChecksum in the Attributes column of the MSI package's File Table will be repaired.
Instructs Windows Installer to rewrite all per-user entries from the MSI package to the Windows system registry. Per-user entries are those entries contained in the HKEY_CURRENT_USER and HKEY_USERS registry hives.
Instructs Windows Installer to rewrite all per-machine entries from the MSI package to the Windows system registry. Per-machine entries are those entries contained in the HKEY_LOCAL_MACHINE and HKEY_CLASSES_ROOT registry hives.
The Patches property page, shown below, lists the patch files that Microsoft Windows Installer will apply to the MSI package during distribution. Each patch will be applied in the order listed in the MSI Patches List.
Click Add > browse to and select the patch file (.msp file or other MSI-based patch file) you want added to the MSI Patches List > click OK to add it to the list. If the patch file is in the same location as the .MSI package, you can simply enter the filename in the MSI Patch File field rather than browsing to and selecting it.
IMPORTANT: The Windows Installer requires direct file access to MSI packages and MSI patch files in order to open them. If a workstation does not have a network client that provides access to the MSI application and MSI patch file (for example, the workstation is using the ZfD Management Agent only), you must force cache the MSI application to the workstation so that the Windows Installer can distribute it from the workstation's cache. You enable the Force Cache option on the Associations page.
If you force cache the application (because either the workstation is using the Management Agent only or you simply want the files available for installation and verification while in disconnected mode) , its patch files must be located in the same directory as the .msi file in order to be cached. When specifying the patch filename in the MSI Patch File field, you must enter the filename only (not the full path).