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
24 VMware, Inc.
Modify the Package.ini File
Use a text editor to modify the Package.ini file.
Modify the Package.ini file
1Open the Package.ini file located in the captured application folder.
For example, a Firefox 2.0.0.3 path might be C:\Program Files\VMware\VMware
ThinApp\Captures\Mozilla Firefox 2.0.0.3\Package.ini.
2 Activate the parameter to edit by removing the semicolon at the beginning of the line.
For example, activate the RemoveSandboxOnExit parameter for Firefox.
RemoveSandboxOnExit=1
3 Delete or change the value of the parameter and save the file.
4 Double-click the build.bat file in the captured application folder to rebuild the application package.
For example, a Firefox 2.0.0.3 path to the build.bat file might be C:\Program Files\VMware\VMware
ThinApp\Captures\Mozilla Firefox 2.0.0.3\build.bat.
Modifying Settings in the ##Attributes.ini File
The ##Attributes.ini file exists in the folder macros of the project folder and applies configuration settings
at the directory level. The Package.ini file applies settings at the overall application level. You can use the
DirectoryIsolationMode, CompressionType, and ExcludePattern parameters in an ##Attributes.ini
file to override the Package.ini settings at the directory level.
For example, you can set the isolation mode at the directory or application level to determine which files and
registry keys are visible and written by the virtual application you create. The detailed setting in the
##Attributes.ini file overrides the overall Package.ini setting. The Package.ini setting determines the
isolation mode only when ThinApp does not have ##Attributes.ini information.
The ##Attributes.ini file appears in most folders for the captured application. For example, the
Attributes.ini file might be located in C:\Program Files\VMware\VMware
ThinApp\Captures\Mozilla Firefox 2.0.0.3\%AppData%\##Attributes.ini.
Modify the ##Attributes.ini File
Use a text editor to modify the ##Attributes.ini file.
Modify the ##Attributes.ini file
1In the ##Attributes.ini file, uncomment, update, or delete the parameter.
2 Double-click the build.bat file in the captured application folder to rebuild the application package.
Capturing Internet Explorer 6 on Windows XP
After you use the Setup Capture wizard to capture Internet Explorer 6 running on Windows XP, on a test
machine you can use the ThinApp ThinDirect plug-in to redirect Web sites or specific pages to automatically
open in a virtual Internet Explorer 6 browser. You can view Web pages that are incompatible in the native
version of Internet Explorer in the virtual Internet Explorer 6. A list is maintained that facilitates a redirection
process for specified incompatible domains and pages.
You can also install Internet Explorer 6 plug-ins such as Java runtime plug-ins. The plug-ins are treated as any
other file during Setup Capture. The plug-ins are embedded in the Internet Explorer 6 capture.
After the ThinDirect plug-in is successfully installed in your native browser, when a user requests a URL that
is included in the redirect list, a message appears in the native browser to alert the user that the page is being
redirected to a virtual Internet Explorer 6 browser. The virtual browser opens and the requested URL appears.