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. 47
Chapter 3 Deploying Applications
Stream ThinApp Packages from the Network
Users can access packaged applications through the network.
Stream packages from the network
1 Place the ThinApp package in a location accessible to client computers.
2 Send a link to users to run the application directly.
Using Captured Applications with Other System Components
Captured applications can interact with other components installed on the desktop.
Performing Paste Operations
Review the following paste operations and limitations with ThinApp:
Pasting content from system installed applications to captured applications – This paste operation is
unlimited. The virtual application can receive any standard clipboard formats, such as text, graphics, and
HTML. The virtual application can receive Object Linking and Embedding (OLE) objects.
Pasting from captured applications to system applications – ThinApp converts OLE objects created in
virtual applications to system native objects when you paste them into native applications.
Accessing Printers
A captured application has access to any printer installed on the computer that it is running on. Captured
applications and applications installed on the physical system have the same printing ability.
You cannot use ThinApp to virtualize printer drivers. You must manually install printer drivers on a computer.
Accessing Drivers
A captured application has full access to any device driver installed on the computer that it is running on.
Captured applications and applications installed on the physical system have the same relationship with
device drivers. If an application requires a device driver, you must install the driver separately from the
ThinApp package.
Sometimes, an application without an associated driver might function with some limitations. For example,
Adobe Acrobat installs a printer driver that enables applications system wide to render PDF files using a print
mechanism. When you use a captured version of Adobe Acrobat, you can use it to load, edit, and save PDF
files without the printer driver installation. Other applications do not detect a new printer driver unless the
driver is installed.
Accessing the Local Disk, the Removable Disk, and Network Shares
When you create a project structure, ThinApp configures isolation modes for directories and registry sub trees.
The isolation modes control which directories the application can read and write to on the local computer.
Review the default configuration options described in Table 3-2.
Table 3-2. Default Configuration Options
Component Description
Hard disk An example of a hard disk is C:\. Isolation modes selected during the
capture process affect access. Users can write to their Desktop and My
Documents folders. Other modifications that the application makes go
into the user sandbox. The default location of the sandbox is in the
Application Data directory.
Removable disk By default, any user who has access rights can read or write to any
location on a removable disk.