4.0.4
Table Of Contents
- ThinApp User’s Guide
- Contents
- About This Book
- Installing ThinApp
- Capturing Applications
- Deploying Applications
- ThinApp Deployment Options
- Establishing File Type Associations with the thinreg.exe Utility
- Building an MSI Database
- Controlling Application Access with Active Directory
- 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 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
- 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
- Sandbox Considerations for Upgraded Applications
- Application Updates That the End User Triggers
- Monitoring and Troubleshooting ThinApp
- Configuring Package Parameters
- Package.ini File Structure
- Parameters that Apply to Package.ini or ##Attributes.ini Files
- Configuring the ThinApp Runtime
- Configuring File System and Registry Isolation
- Configuring File and Protocol Associations
- Configuring Build Output
- Configuring Permissions and Security
- Configuring Objects and DLL Files
- Configuring Storage
- Configuring Processes and Services
- Configuring File and Block Sizes
- Configuring Icons
- Configuring Logging
- Configuring Versions
- Configuring Locale Information
- Configuring Individual Applications
- Configuring Dependent Applications with Application Link
- Configuring Application Updates with Application Sync
- Configuring MSI Files
- Configuring Sandbox Storage and Inventory Names
- ThinApp Sandbox
- Snapshot Commands and Customization
- ThinApp Virtual File System
- ThinApp Scripts
- Callback Functions
- Use Scripts in a ThinApp Environment
- API Functions
- Glossary
- Index
ThinApp User’s Guide
104 VMware, Inc.
Using Folder Macros
ThinAppusesmacrostorepresentfilesystempathlocationsthatmightchangewhenvirtualizedapplications
runondifferentWindowsoperatingsystemsorcomputers.Theuseofmacrosallowssharedapplication
profileinformationtoinstantlymigratetodifferentoperatingsystems.
Forexample,youmightcaptureanapplicationonasystemthathas
C:\WINNTastheWindowsdirectoryand
deploytheapplicationonasystemthathasC:\WindowsastheWindowsdirectory.ThinApptransparently
convertsC:\WINNTto%SystemRoot%duringthecaptureprocessforthat systemandexpands%SystemRoot%
toC:\Windowsduringruntimeforthatsystem.
IfanapplicationregistersDLLstoC:\winnt\system32whilerunning
onWindows 2000,theusercanquit
theapplicationandlogintoaWindowsXPmachine.OntheWindowsXPmachine,thefilesappeartoexistat
C:\windows\system32andallrelatedregistrykeyspointtoC:\windows\system32.
OnWindowsVista,ThinAppmovesWindowsSxSDLLsandpolicyinformationtomatchWindows
Vista
insteadofusingWindowsXPfilepathstyles.Thisfeatureallowsmostapplicationstomigratetoupdatedor
olderoperatingsystems.
ThinAppprovidesSxSsupportforapplicationsrunningonWindows2000eventhoughtheunderlying
operatingsystemdoesnot.ThissupportenablesmostapplicationscapturedonWindowsXPto
runon
Windows2000withoutchanges.
List of Folder Macros
ThinAppusestheshfolder.dllfiletoobtainthelocationofshellfolders.Olderversionsofthe
shfolder.dllfiledonotsupportsomemacronames.
Macrosrequiringshfolder.dllversion5.0orlaterinclude%ProgramFilesDir%,%Common AppData%,
%Local AppData%,%My Pictures%,and%Profile%.
Macrosrequiringshfolder.dllversion6.0orlaterinclude%My Videos%,%Personal%,
and%Profiles%.
Table D‐1liststheavailablefoldermacros.
Table D-1. Folder Macros
Macro Name Typical Location
%AdminTools% C:\Documents and Settings\<user_name>\Start
Menu\Programs\Administrative Tools
%AppData% C:\Documents and Settings\<user_name>\Application Data
%CDBurn Area% C:\Documents and Settings\<user_name>\Local Settings\Application
Data\Microsoft\CD Burning
%Common AdminTools% C:\Documents and Settings\All Users\Start Menu\Programs\Administrative
Tools
%Common AppData% C:\Documents and Settings\All Users\Application Data
%Common Desktop% C:\Documents and Settings\All Users\Desktop
%Common Documents% C:\Documents and Settings\All Users\Documents
%Common Favorites% C:\Documents and Settings\All Users\Favorites
%Common Programs% C:\Documents and Settings\All Users\Start Menu\Programs
%Common StartMenu% C:\Documents and Settings\All Users\Start Menu
%Common Startup% C:\Documents and Settings\All Users\Start Menu\Programs\Startup
%Common Templates% C:\Documents and Settings\All Users\Templates
%Cookies% C:\Documents and Settings\<user_name>\Cookies
%Desktop% C:\Documents and Settings\<user_name>\Desktop
%Drive_c% C:\
%Drive_m% M:\