Select .msi File

Use this option if you want the .msi file copied to the ZENworks® Server and then distributed from the ZENworks Server to assigned users and devices. This is referred to a normal install because ZENworks Adaptive Agent copies the .msi file to the managed device’s local drive and then the Microsoft^* Windows^* Installer program installs the application from the local .msi file.

Click to display the Select .msi File dialog box. Click Browse to select the .msi file to upload. Select the Include all files in and below the directory of this file option to include all the supporting files that are within the directory or subdirectory containing the .msi file.

Use this option if you want the Microsoft Windows Installer program to install the application from the .msi file on a network location. You must specify the complete path to the .msi file to use as the source file during distribution to the workstation.

You can use a mapped drive or UNC path. If you use a drive mapping, you must ensure that all workstations have the same drive mapped to the source location. For this reason, we recommend that you specify a UNC path.

After you create the MSI bundle, you cannot change the .msi filename; however, you can change the path to the .msi file. If you change the .msi filename, the installation fails.

Click to display the Install Parameters dialog box, then specify the desired parameters. Click the Help button for additional information.

Click to display the Uninstall Parameters dialog box, then specify the desired parameters. Click the Help button for additional information.

Click to display the Repair Parameters dialog box, then specify the desired parameters. Click the Help button for additional information.

Click Add to browse to and select the desired transform file. You can upload the transform file or you can specify its location.

Different groups within an organization often use the same application, but that doesn’t mean they require the same feature set. One of the benefits of Windows Installer is that if you have 10 groups needing 10 different feature sets or other alterations for the same application, you can deploy the same MSI package to all 10 user groups, but with a different transform file (MST) applied for each group.

A transform file is a collection of changes applied to an MSI installation. It contains all modification information, such as whether features are installed; how they are installed; which files, shortcuts, and registry entries are included; and Add/Remove Programs applet information.

If you have vendor-supplied MSI packages, you can use FLEXnet^* AdminStudio 7.5 ZENworks Edition to create and manage transforms.

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 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 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.