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. 69
Chapter 5 Locating the ThinApp Sandbox
Controlling the Sandbox Location
The setup capture process adds the SandboxName parameter to the Package.ini file. If you capture Firefox
and Mozilla Firefox 3.0 is the value of this parameter, the default location of the sandbox for the
application is %AppData%\Thinstall\Mozilla Firefox 3.0. The typical %AppData% location is
C:\Documents and Settings\<user_name>\Application Data. %AppData% is often mapped to a shared
network drive.
Store the Sandbox on the Network
You can use the SandboxPath parameter to store the sandbox on a mapped drive. A network location is useful
for backing up the sandbox and for users who log in to any machine and keep their application settings. For
more information about the SandboxPath parameter, see “SandboxPath” on page 97.
Store the sandbox on a mapped drive
1Open the Package.ini file.
2 Under the SandboxName parameter, set the SandboxPath parameter to the network location.
SandboxName=Mozilla Firefox 3.0
SandboxPath=Z:\Sandbox
For example, if Mozilla Firefox 3.0 is the value of the SandboxName parameter, the captured Firefox
application creates the sandbox in Z:\Sandbox\Mozilla Firefox 3.0.
Store the Sandbox on a Portable Device
You can use the SandboxPath parameter to set a portable device location for the sandbox. You can use any
portable device, such as a USB drive, that appears as a disk drive in the My Computer system folder. A portable
device location is useful to keep the sandbox data on the device where the application resides.
For more information about the SandboxPath parameter, see “SandboxPath” on page 97.
Store the sandbox in the same directory on a USB drive where the executable file resides
1Open the Package.ini file.
2 Under the SandboxName parameter, set the SandboxPath parameter to this value.
SandboxName=Mozilla Firefox 3.0
SandboxPath=.
For example, if Mozilla Firefox 3.0 is the value of the SandboxName parameter, the captured Firefox
application creates the Mozilla Firefox 3.0 sandbox in the same directory that Firefox runs from.
Store the Sandbox in a Thinstall Directory on a USB Drive at the Same Level as the
Executable File
The sandbox in a Thinstall directory located on a USB drive must be stored at the same level at which the
executable file is stored.
Store the sandbox in a Thinstall directory on a USB drive at the same level as the executable file
1If the %THINSTALL_SANDBOX_DIR% or %<sandbox_name>_SANDBOX_DIR% environment variables are set,
unset the variables.
2 On the portable device, create a Thinstall directory in the same directory as your captured application.
The next time the packaged application starts from the portable device, the application creates a sandbox
in the Thinstall directory.
3 If the application and sandbox originally ran from another location, such as a computer local hard drive,
and you need the same sandbox on a portable device, copy the Thinstall directory from %AppData% to
the directory where the executable file resides on the device.
ThinApp no longer uses the sandbox in the original location.