5.1

VMware, Inc. 15
2
You can capture applications to package an application into a virtual environment.
The Setup Capture wizard is the main method to capture applications and set initial application parameters.
Advanced users who must capture applications from the command line can use the snapshot.exe utility
instead of the Setup Capture wizard.
This section includes the following topics:
 “Phases of the Capture Process” on page 15
 “Preparing to Capture Applications” on page 15
 “Capturing Applications with the Setup Capture Wizard” on page 16
 “Advanced Package Configuration” on page 23
 “Capturing Internet Explorer 6 on Windows XP” on page 24
 “Capturing Multiple Application Installers with ThinApp Converter” on page 26
 “ThinApp Package Management” on page 34
Phases of the Capture Process
Capturing an application involves system scans, application configuration, package configuration, and
generation of the virtual application for distribution.
The Setup Capture wizard sets initial parameters for the application. You can customize the full set of
parameters outside of the wizard.
Preparing to Capture Applications
Preparing for the capture process involves understanding the needs and dependencies of the application.
For target applications that have dependencies on other applications, libraries, or frameworks, you can capture
the dependencies or use the Application Link utility to link separate virtual applications at runtime. For
information about the Application Link utility, see “Application Link Updates” on page 54.
For target applications that require locale formats, such as a specific date format, you can capture them in an
environment with the required locale setting. ThinApp runs virtual applications according to the regional and
language settings on the capture system rather than the settings on the system that runs the application.
Although you can modify the default locale setting by commenting out the LocaleIdentifier parameter in
the Package.ini file and rebuilding the application, you can avoid complications in the capture environment.
For information about the LocaleIdentifier parameter, see “LocaleIdentifier” on page 83.
Capturing Applications
2