5.1
Table Of Contents
- ThinApp User’s Guide
- Contents
- About This Book
- Installing ThinApp
- Capturing Applications
- Phases of the Capture Process
- Preparing to Capture Applications
- Capturing Applications with the Setup Capture Wizard
- Create a System Image Before the Application Installation
- Rescan the System with the Installed Application
- Defining Entry Points as Shortcuts into the Virtual Environment
- Set Entry Points
- Manage with VMware Horizon Application Manager
- Set User Groups
- Defining Isolation Modes for the Physical File System
- Set File System Isolation Modes
- Storing Application Changes in the Sandbox
- Customize the Sandbox Location
- Send Anonymous Statistics to VMware
- Customize ThinApp Project Settings
- Defining Package Settings
- Customize Package Settings
- Opening Project and Parameter Files
- Build Virtual Applications
- Advanced Package Configuration
- Capturing Internet Explorer 6 on Windows XP
- Capturing Multiple Application Installers with ThinApp Converter
- ThinApp Package Management
- Deploying Applications
- ThinApp Deployment Options
- Establishing File Type Associations with the thinreg.exe Utility
- Building an MSI Database
- Controlling Application Access with Active Directory
- Starting and Stopping Virtual Services
- Using ThinApp Packages Streamed from the Network
- Using Captured Applications with Other System Components
- Performing Paste Operations
- Accessing Printers
- Accessing Drivers
- Accessing the Local Disk, the Removable Disk, and Network Shares
- Accessing the System Registry
- Accessing Networking and Sockets
- Using Shared Memory and Named Pipes
- Using COM, DCOM, and Out-of-Process COM Components
- Starting Services
- Using File Type Associations
- Sample Isolation Mode Configuration Depending on Deployment Context
- Updating and Linking Applications
- Application Updates That the End User Triggers
- Application Sync Updates
- Using Application Sync in a Managed or Unmanaged Environment
- Update Firefox 2.0.0.3 to Firefox 3 with Application Sync
- Fix an Incorrect Update with Application Sync
- Application Sync Effect on Entry Point Executable Files
- Updating thinreg.exe Registrations with Application Sync
- Maintaining the Primary Data Container Name with Application Sync
- Completing the Application Sync Process When Applications Create Child Processes
- Application Link Updates
- View of the Application using Application Link
- Link a Base Application to the Microsoft .NET Framework
- Set Up Nested Links with Application Link
- Affecting Isolation Modes with Application Link
- PermittedGroups Effect on Linked Packages
- Sandbox Changes for Standalone and Linked Packages
- Import Order for Linked Packages
- File and Registry Collisions in Linked Packages
- VBScript Collisions in Linked Packages
- VBScript Function Order in Linked Packages
- Storing Multiple Versions of a Linked Application in the Same Directory
- Using Application Sync for a Base Application and Linked Packages
- Application Sync Updates
- Application Updates That the Administrator Triggers
- Automatic Application Updates
- Upgrading Running Applications on a Network Share
- Application Synchronization Using Group Policy Object
- Sandbox Considerations for Upgraded Applications
- Updating the ThinApp Version of Packages
- Application Updates That the End User Triggers
- Locating the ThinApp Sandbox
- Creating ThinApp Snapshots and Projects from the Command Line
- ThinApp File System Formats and Macros
- Creating ThinApp Scripts
- Callback Functions
- Implement Scripts in a ThinApp Environment
- API Functions
- Monitoring and Troubleshooting ThinApp
- Glossary
- Index
ThinApp User’s Guide
32 VMware, Inc.
PackageIniOverrideFile
Specify the file path to the global Package.ini override file.
This optional parameter enables you to specify a global override file for Package.ini that is generated for
each ThinApp project. The values in the override file are merged into Package.ini in the ThinApp project
that is generated for each application.
Global overrides are useful when you have a global policy setting, for example, PermittedGroup in
Package.ini.
A Package.ini override file is formatted like a standard Windows INI file. You can add INI parameters and
values that are relevant to the Package.ini file.
The path is relative to the application installer’s network share. Using the example for specifying the network
shares for the application installers and ThinApp projects, if you specify
PackageIniOverrideFile=override.ini, ThinApp Converter will try to find the file under
\\AppInstallerServer\AppInstaller. You can provide a more explicit value by using predefined
variables. For more information, see “Predefined Environment Variables” on page 33.
You can specify a Package.ini file for each application. This process is described as part of the
[AppSettings:AppName] section.
ExclusionList
Specify a comma- or semicolon-separated list of application directories that ThinApp will skip when searching
for application installers.
The list is case insensitive.
You can specify wildcards for DOS-style file names. For example, Microsoft*. ? and * are supported.
Example
Following is an example of an exclusion specification using a wildcard.
[Settings]
ExclusionList=App?.old;FireFox1.0
ProjectPostProcessingCommand
Specify the file path to the project post processing command.
The file path is relative to the application installer’s network share. Using the example for specifying the
network shares for the application installers and ThinApp projects, if you specify
ProjectPostProcessingCommand=addscript.bat, ThinApp Converter will try to find the file under
\\AppInstallerServer\AppInstaller. You can provide a more explicit value by using predefined
variables. For more information, see “Predefined Environment Variables” on page 33.
StopOnError
Specify whether ThinApp Converter should stop converting an application if it encounters an error, or
continue with the other applications. The default value is false.
BuildAfterCapture
Specify whether the ThinApp Converter should build the ThinApp Projects into packages following capture.
The default value is true.
DetectIdle
Specify whether ThinApp Converter should try to detect if an application installer is stalled, for example when
the application is waiting for user input on the guest virtual machine because incorrect silent installation
switches were specified.
The default value is true. ThinApp Converter might not be able to detect all situations in which the installer
is idle.










