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
34 VMware, Inc.
Example
Following is an example of how predefined variables can be used in the PackageIniOverrideFile,
ProjectPostProcessingCommand, and InstallationCommand parameters.
[Settings]
PackageIniOverrideFile=%AppInstallersRootDir%\AppSyncSettings.ini
;will resolve to \\AppInstallerServer\AppInstaller\AppSyncSettings.ini
[AppSettings:Adobe]
InstallationCommand=AdbeRdr920_en_US.exe /sAll
PackageIniOverrideFile=%AppInstallerDir%\override.ini
;will resolve to \\AppInstallerServer\AppInstaller\Adobe\AppSyncSettings.ini
ThinApp Package Management
In the earlier versions of ThinApp, to change certain Package.ini parameters, you had to first make those
changes in the configuration file, save the file, and rebuild it.
Using the ThinApp package management feature, you can dynamically reconfigure the attributes of deployed
ThinApp packages at runtime.ThinApp Package management helps IT administrators manage ThinApp
packages and define group policy for each package.
Each package to be managed must have an associated group policy defined using its inventory name.
Selecting Policy Precedence
In ThinApp 5.1 you have the option of defining group policy for a specific set of client systems.
In the following example, T1, T2, T3 and T4 represent four instances of the same package. To define multiple
group policies for a package at runtime, you must select the required attribute, modify it, and set the group
policy. The T2 ThinApp package has two group policies defined for a single package.
ThinApp selects the policy precedence when you rebuild the package and deploy it on the system. If a package
contains a group policy, ThinApp gives precedence to the policy over the Package.ini configuration.
Group Policy Administrative Template
ThinApp 5.1, introduces the Group Policy Administrative Template (ADMX/ADML) files. With these template
files, you can reconfigure Group Policy settings for applications that were packaged by using ThinApp. The
GPO files work on domain controllers that run in the following environment:
Windows Server 2008
Windows Server 2008 R2
Windows Server 2012
In ThinApp 5.1, you can reconfigure or manage the following attributes of a deployed package:
AppSync
AppLink
Entry-Point Shortcuts
Table 2-1. Group Policy Precedence table
Package Group Policy 1 Group Policy 2 Group Policy 3 Group Policy 4
T1 YesNoNoNo
T2 No Yes No Yes
T3 No No Yes No
T4 No No No Yes










