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. 63
Chapter 4 Updating and Linking Applications
3 Create a desktop or Start menu shortcut to the user’s desktop that points to a shared executable file
location at \\<server>\<share>\Firefox.exe.
Assume two users start Firefox.exe and lock the application.
4 Copy the updated version of Firefox.exe to the central share at
\\<server>\<share>\Firefox.exe.1.
If you are a new user, ThinApp starts the application with the new package data in Firefox.exe.1. If
you are a user working with the original version, you can see the new version after you exit the application
and restart the application.
5 If you must deploy a more current update of Firefox, place it in the same directory with a higher number
at the end.
6 Copy Version 2.0 of Firefox.exe to central share at \\<server>\<share>\Firefox.exe.2
After both Firefox.exe and Firefox.exe.1 are unlocked, you can delete Firefox.exe and rename
Firefox.exe.1 to Firefox.exe. This permanently replaces the older version with the newer
version.ThinApp always uses the filename that has the highest version number. If you must roll back to an
earlier version and the most recent version is locked, copy the old version so that it has the highest version
number.
N
OTE If you have a project with an.alt file, the .alt file from the new version must also be copied and
renamed. The number used in the filename must come before the .alt extension for example, Firefox.alt
becomes Firefox.1.alt. Changes to Package.ini will not be seen if the primary data container is a .dat
file. A workaround is to rebuild the project with an .exe primary data container if it is under 2GB in size.
Application Synchronization Using Group Policy Object
In ThinApp 5.1, you can use the Group Policy Object to configure the Appsync feature. In the earlier versions
of ThinApp, these parameters were present in the Package.ini file, and you had to configure them by using
the registry. In ThinApp 5.1 you can create policy files by using the AppPolicy.exe. ThinApp installer now
contains the following files:
ThinAppBase.admx
ThinAppBase.adml
ThinAppGeneric.admx
ThinAppGeneric.adml
AppPolicy.exe
The administrative template files ThinAppGeneric.admx and ThinAppGeneric.adml provide a template, on
which the configuration for a specific Package will be based. Ensure that the generic template files
ThinAppGeneric.admx and ThinAppGeneric.adml are present in the same working directory as
AppPolicy.exe.
Configure Application Synchronization
You will update Adobe Reader from IX to X using the AppSync option.
1 On the Domain Controller, copy the ThinAppBase.admx file to C:\Windows\PolicyDefinitions
directory.
2Copy the ThinAppBase.adml file to C:\Windows\PolicyDefinitions\en-US.
3 In the ThinApp directory, run the command AppPolicy.exe /c “Adobe Reader”
The tool generates two template files ThinApp_InventoryName.admx and
ThinApp_InventoryName.adml in the ThinApp Policy directory. If you are capturing Adobe Reader
for application synchronization then these files would be ThinApp_AdobeReader.admx and ThinApp_
AdobeReader.adml. You have to add these two files to the GPO.