VMware THINAPP 4.6 - MIGRATING APPLICATIONS TECHNICAL NOTE, Руководство пользователя

Страница: 43 / 146

VMware, Inc. 43
Chapter 3 Deploying Applications
Building an MSI Database
If you do not create MSI files during the capture process, you can still create these files after building an
application. An MSI database is useful for delivering captured applications through traditional desktop
management systems to remote locations and automatically creating shortcuts and file type associations.
Basic Active Directory group policies provide ways to distribute and start MSI packages.
ThinApp creates an MSI database that contains captured executable files, installer logic, and the thinreg.exe
utility.
Customizing MSI Files with Package.ini Parameters
You can customize the behavior of MSI files by modifying Package.ini parameters and rebuilding the
application package.
The following parameters can affect MSI configuration:

The MSIInstallDirectory parameter sets the installation directory for the package.
For example, include MSIInstallDirectory=C:\Program Files\ in the Package.ini file.

The MSIDefaultInstallAllUsers parameter sets the installation of the package for individual users.
ThinApp installs the package in the %AppData% user directory.
For example, include MSIDefaultInstallAllUsers=0 in the Package.ini file.
For more information about this parameter, see “Specifying a Database Installation for Individual Users
and Machines” on page 44.

The MSIFileName parameter names the package.
For example, include MSIFilename=Firefox30.msi in the Package.ini file.

The MSIRequireElevatedPrivileges parameter indicates whether an installer needs elevated
privileges for deployment on Microsoft Vista. Installations for individual users do not usually need
elevated privileges but per ‐ machine installations require such privileges.
For example, include MSIRequireElevatedPrivileges=1 in the Package.ini file.

The MSIProductCode parameter makes it easier to install a new version of the application. An MSI
database contains a product code and an upgrade code. When you update a package, keep the original
value of the MSIUpgradeCode parameter.
If the parameter value of the new version is the same as the value of the old version, the installation
prompts you to remove the old version. If the values for the parameter are different, the installation
uninstalls the old version and installs the new version.
VMware recommends that you avoid specifying an MSIProductCode value and allow ThinApp to
generate a different product code for each build.
Regardless of the parameter values specified at build time, you can override the settings at deployment time.
See “Force MSI Deployments for Each User or Each Machine” on page 44. For more information about MSI
parameters, see “Configuring MSI Files” on page 96.
Modify the Package.ini File to Create MSI Files
For more information about MSI parameters, see “Customizing MSI Files with Package.ini Parameters” on
page 43 and “Configuring MSI Files” on page 96.
Before you can modify MSI parameters, you must add an entry for the MSIFilename parameter to generate
MSI files.