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
22 VMware, Inc.
Customize Package Settings
The capture process includes initial settings for the primary data container, MSI packages, and executable
package compression.
Customize package settings in the Setup Capture wizard
1On the Package Settings page, select the primary data container from the list that is based on your
executable file entry points.
If the size of the primary container is smaller than 200MB, ThinApp creates a .exe file as the primary
container. For a small application such as Firefox, any .exe file can serve as the main data container.
If the size of the primary container is larger than 200MB, ThinApp creates a separate.dat file as the
primary container because Windows XP and Windows 2000 cannot show shortcut icons for large
.exe files. Generating separate small .exe files together with the .dat file fixes the problem.
If the size of the primary container is between 200MB and 1.5GB, ThinApp creates the default .dat
file unless you select a .exe file to override the default .dat file.
2(Optional) If you select a .exe file to override the default .dat file when the size of the primary container
is between 200MB and 1.5GB, ignore the generated warning.
Selecting a .exe file enables all applications to work properly but might prevent the proper display of
icons.
3 (Optional) If you cannot select a primary data container, type a primary data container name to generate
a .dat file.
If you plan to use the Application Sync utility to update a captured application, ThinApp uses the primary
data container name during the process. You must use the same name across multiple versions of the
application. You might not be able to select the same primary data container name from the list.
For example, Microsoft Office 2003 and Microsoft Office 2007 do not have common entry point names.
4 (Optional) Select the Generate MSI package check box and change the MSI filename.
5 (Optional) To create a smaller executable package for locations such as a USB device, select the Compress
virtual package check box.
6Click Save.
Opening Project and Parameter Files
The capture process provides an opportunity to review the project files to update settings before building the
executable package or MSI package.
For example, if you capture Firefox 2.0.0.3, you might browse the C:\Program Files\VMware\VMware
ThinApp\Captures\Mozilla Firefox 2.0.0.3 directory to update a setting, such as an Active Directory
specification, in the Package.ini file that contains the parameters set during the capture process. For
information about updating settings, see “Advanced Package Configuration” on page 23.
The project includes folders, such as %AppData%, that represent file system paths that might change locations
when running on different operating systems or computers. Most folders have ##Attributes.ini files that
specify the isolation mode at the folder level.










