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
48 VMware, Inc.
Accessing the System Registry
By default, captured applications can read the full system registry as permitted by access permissions. Specific
parts of the registry are isolated from the system during the package creation process. This isolation reduces
conflicts between different versions of virtual applications and system-installed applications. By default,
ThinApp saves all registry modifications from captured applications in an isolated sandbox and the system
remains unchanged.
Accessing Networking and Sockets
Captured applications have standard access to networking features. Captured applications can bind to local
ports and make remote connections if the user has access permissions to perform these operations.
Using Shared Memory and Named Pipes
Captured applications can interact with other applications on the system by using shared memory, named
pipes, mutex objects, and semaphores.
ThinApp can isolate shared memory objects and synchronization objects. This isolation makes them invisible
to other applications, and other application objects are invisible to a captured application.
Using COM, DCOM, and Out-of-Process COM Components
Captured applications can create COM controls from the virtual environment and the system. If a COM
control is installed as an out-of-process COM, the control runs as a virtual process when a captured application
uses it. You can control modifications that the captured applications make.
Starting Services
Captured applications can start and run system-installed services and virtual services. System services run in
the virtual environment that controls the modifications that the services can make.
Using File Type Associations
Captured applications can run system-installed applications by using file type associations. You can add file
type associations to the local computer registry to point to captured executable files for individual users and
machines.
Network mapped drives By default, any user who has access rights can read or write to any
location on a network mapped disk.
UNC network paths By default, any user who has access rights can read or write to any
location on a UNC network path.
Table 3-2. Default Configuration Options (Continued)
Component Description