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
use Microsoft Office 2003 and Microsoft Office 2007 as inventory names rather than just Microsoft Office.
When you maintain different versions of a virtual application in the same environment, you might want to
change the SandboxName parameter to ensure that a new version has isolated user settings in a different
sandbox.
If you have a package that includes other applications, you might update the inventory name manually to
reflect the true contents of the package. For example, if you capture the SuperApp application and the
package includes Java Runtime, the InventoryName value might appear as Java Runtime Environment 1.5
instead of SuperApp. The Add or Remove Programs window displays the first application installed within
the package.
Example: Modifying the InventoryName Parameter
You can modify the InventoryName parameter to Microsoft Office 2003.
[BuildOptions]
InventoryName=Microsoft Office 2003
RemoveSandboxOnExit Parameter
The RemoveSandboxOnExit parameter deletes the sandbox and resets the application when the last child
process exits.
ThinApp stores all application changes to the registry and file system locations with WriteCopy or Full
isolation mode in the sandbox. ThinApp sets an initial value for theRemoveSandboxOnExit parameter that
maintains consistent settings for the sandbox directory across multiple application runs.
If the application creates child processes, ThinApp does not delete the sandbox until all child processes exit.
Applications might be designed to leave child processes in place, which can block the cleanup operation. For
example, Microsoft Office 2003 leaves the ctfmon.exe process. You can use a script to end the ctfmon.exe
process and child processes to force the cleanup operation to occur.
You can decide at runtime whether to use the RemoveSandboxOnExit script API function to delete the
sandbox on exit.
Example: Modifying the RemoveSandboxOnExit Parameter
You can modify the RemoveSandboxOnExit to delete the sandbox when multiple users share an application
under one user name, you can delete the sandbox to eliminate the previous user’s registry and file system
changes.
[BuildOptions]
RemoveSandboxOnExit=1
SandboxName Parameter
The SandboxName parameter specifies the name of the directory that stores the sandbox. Thinapp sets an
initial value that uses the inventory name as the sandbox name.
When you upgrade an application, the sandbox name helps determine whether users keep previous
personal settings or require new settings. Changing the sandbox name with new deployments affects the
need to create a sandbox with different settings or keep the same sandbox.
Example: Modifying the SandboxName Parameter
When you update an application and want to use new user preferences for the application, you can modify
the SandboxName parameter to reflect the updated version.
[BuildOptions]
SandboxName=My Application 2.0
ThinApp Package.ini Parameters Reference Guide
76 VMware, Inc.










