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
104 VMware, Inc.
L logging.dll
A utility that generates .trace files.
Log Monitor
A utility that captures chronological activity for executable files that the captured application starts.The
log_monitor.exe file is compatible only with applications captured using the same version of ThinApp.
M MSI
A Windows Installer container that is useful for application deployment tools. You can deliver the
captured application as an MSI file instead of an executable file.
N native
Refers to the physical environment rather than the virtual environment. See also physical.
network streaming
The process of running a package from a central server. ThinApp downloads blocks of the application as
needed to ensure quick processing and display.
P package
The virtual application files that the ThinApp build process generates. The package includes the primary
data container file and entry point files to access the application.
package.ini
The file that applies configuration settings to the package and that resides in the captured application
folder. The Setup Capture wizard sets the initial values of the configuration settings.
physical
Refers to the computer memory and file system in which all standard Windows processes run. Depending
on ThinApp isolation mode settings, processes in the virtual environment can access the physical
environment. See also native, virtual.
postscan
To establish an image or snapshot of a machine after you install the application you want to capture. The
capture process stores in a virtual file system and virtual registry the differences between the prescan and
postscan images. See also prescan, snapshot.
prescan
To establish a baseline image or snapshot of a machine before you install the application you want to
capture. The capture process stores in a virtual file system and virtual registry the differences between the
prescan and postscan images. See also postscan, snapshot.
primary data container
The main virtual application file. The file is a .exe file or a .dat file that includes the ThinApp runtime
and the read-only virtual file system and virtual registry. The primary data container must reside in the
same /bin directory with any subordinate application executable files because entry points use the
information in the primary data container.
project
The data that the capture process creates before you build a package. The capture process uses the
inventory name as the default project directory name. You can customize parameters in the project files
before you build an application package. You cannot deploy a captured application until you build a
package from the project.










