5.1
Table Of Contents
- ThinApp Package.ini Parameters Reference Guide
- Contents
- About This Guide
- Configuring Package Parameters
- Package.ini File Structure
- Package.ini or ##Attributes.ini Files That Override Package.ini Settings
- Configuring the ThinApp Runtime
- Configuring Isolation
- Configuring File and Protocol Associations
- Configuring Build Output
- Configuring Permissions
- Configuring Objects and DLL Files
- ExternalCOMObjects Parameter
- ExternalDLLs Parameter
- ForcedVirtualLoadPaths Parameter
- IsolatedMemoryObjects Parameter
- IsolatedSynchronizationObjects Parameter
- NotificationDLLs Parameter
- NotificationDLLSignature Parameter
- ObjectTypes Parameter
- SandboxCOMObjects Parameter
- VirtualizeExternalOutOfProcessCOM Parameter
- Configuring File Storage
- Configuring Processes and Services
- Configuring Sizes
- Configuring Logging
- Configuring Versions
- Configuring Locales
- Configuring Individual Applications
- Configuring Dependent Applications Using the Application Utility
- Configuring Application Updates with the Application Sync Utility
- Configuring MSI Files
- Configuring Sandbox Storage and Inventory Names
- Other Configuration Parameters
- DisableCutPaste Parameter
- LoadDotNetFromSystem Parameter
- PermittedComputers Parameter
- Services Parameter
- StatusbarDisplayName Parameter
- DisableTransactionRegistry Parameter
- PreventDLLInjection
- ProcessExternalNameBehavior Parameter
- PreventDllInjectionExceptions Parameter
- LargeAddressAware Parameter
- PermittedComputers Parameter
- PermittedComputersAccessDeniedMsg Parameter
- PermittedComputersOfflineAccess Parameter
- IgnoreDDEMessages Parameter
- Locating the ThinApp Sandbox
- Controlling the Sandbox Location
- Sandbox Structure
- Creating ThinApp Snapshots and Projects from the Command Line
- Index
MSIUpgradeCode Parameter
The MSIUpgradeCode parameter specifies a code for the MSI database that facilitates updates. When two
packages, such as the version 1.0 package and the version 2.0 package, have the same upgrade code, the MSI
installer detects this link, uninstalls the earlier package, and installs the updated package.
The capture process generates a random upgrade code based on the inventory name. To ensure that the MSI
database versions have the same upgrade code, keep the same inventory name across versions of the
MSIwrapper. For information about the inventory name, see “InventoryName Parameter,” on page 75.
The parameter is applied only when the MSIFilename parameter requests the generation of a Windows
Installer database.
NOTE Do not modify the UpgradeCode value unless the new value is a valid GUID.
Example: Creating an MSIFile using MSIUpgradeCode Parameter
The capture process can create an MSI file with D89F1994-A24B-3E11-0C94-7FD1E13AB93F as the upgrade
code.
[BuildOptions]
MSIFilename=mymsi.msi
MSIUpgradeCode={D89F1994-A24B-3E11-0C94-7FD1E13AB93F}
MSIStreaming Parameter
The MSIStreaming parameter determines the use of .cab files that can affect application performance.
The default setting is MSIStreaming=0. With this value, the packaged .exe files and .dat files are compressed
in the .cab file. Disabling the parameter in Package.ini has the same effect as setting the value to 0. When
the MSI runs, the packaged files are extracted to the Program Files directory of the Windows operating
system, and registered either to the user or the system, depending on other Package.ini settings.
Setting the parameter value MSIStreaming=1, results in the packaged.exe files and.dat files being excluded
from the .cab file, and subsequently from the .msi file. This value enables a choice to be made during
deployment between registering the application from a network share or installing in theProgram Files
directory of the Windows operating system.
If you set this value, ensure that both the MSI and the .exe and .dat files of the ThinApp package are
available on the network share.
Example: Modifying the MSIStreaming Parameter
You can modify the MSIStreaming parameter to ignore a .cab file when it slows down the installation
process for applications. You can distribute the MSI file and individual executable files in the /bin directory
to install the application.
[BuildOptions]
MSIStreaming=1
Chapter 20 Configuring MSI Files
VMware, Inc. 73