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
VMware, Inc. 59
Chapter 4 Updating and Linking Applications
Forcing an Application Sync Update on Client Machines
You can use the AppSync command to force an Application Sync update on a client machine. You might want
to update a package stored in a location where standard users do not have write access. In this situation, you
cannot use Application Sync parameters to check for updates when an application starts because users do not
have the required rights to update the package. You can schedule a daily AppSync.exe run under an account
with sufficient privileges. The Application Sync parameters, such as AppSyncUpdateFrequency, in the
Package.ini file do not affect the AppSync command.
To force an Application Sync update, use the AppSync <Application_Sync_URL>
<executable_file_path> command. The value of the URL is the same as the Application Sync URL in the
Package.ini file and the executable file path is the path to the executable file that requires the update.
Application Linking Using Group Policy Object
Configure AppLink for FF28
You will configure AppLink to QuickTime for the FF28 application.
1 In Policies folder, navigate to FF28 and click Configure AppLink for FF28.
2 In the Configure AppLink for FF28, select Enabled.
3Click Show next to Require AppLinks.
4Copy the QuickTime7 plug-in value, paste it in the Required AppLinks text box, and click OK.
The FF28 application running on all machines belonging to this domain now fetches the QuickTime 7.7.dat
from this location.
5 Specify some value (a space) for Optional AppLinks and click Apply.
Link the Group Policy against the Domain Scope
You will associate the configured AppLink to the required domain.
1 In GPMC, navigate to your domain and right click your domain.
2 From the pop-up menu, select link to an existing GPO.
3 In the Select GPO window select FF28 and click OK.
4 After linking the GPO to the domain, select a virtual machine that has the new FF28 instance.
5 Start the FF28 and open a file with QuickTime content. The application displays the following message:
A plug-in is needed to play this content. Install plug-in….
Verify the Virtual Application after a Group Policy Update
1 On the client virtual machine, login as administrator and run 'gpupdate /force' in command prompt.
2 This will update the policy immediately, otherwise you can wait till the next policy update interval
finishes.
To verify the policy update, perform the following steps:
1 On the client virtual machine, type regedit.
2 Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Policies > ThinApp > Management >FF28 >
AppLink > Required AppLink.
You can see that the required AppLink has a link which points to the QuickTime.dat path defined in the GPO.
With this option, a running virtual ThinApp application can check whether it has a group policy associated
with it by the inventory name. If a policy exists, that policy will have precedence over the Package.ini
configuration, however, this change will be effective only on next launch of the application.
The Configure AppLink feature has the following options: