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
42 VMware, Inc.
Modify the MSI parameters
1In the Package.ini file, type the MSI filename.
MSIFilename=<filename>.msi
For example, the filename for Firefox might be Mozilla Firefox 2.0.0.3.msi.
2 (Optional) Update other MSI parameters.
3 Double-click the build.bat file in the captured application folder to rebuild the application package.
Specifying a Database Installation for Individual Users and Machines
You can modify the installation of the MSI database for users and machines.
ThinApp installs the MSI database across all machines. You can change the default installation with the
following parameter values:
To create a database installation for individual users, use a value of 0 for the
MSIDefaultInstallAllUsers parameter in the Package.ini file. This value creates msiexec
parameters for each user.
To allow administrators to create a database installation for all users on a machine, or to allow an
individual user without administrator rights to create an installation only for that user, use a value of 2
for the MSIDefaultInstallAllUsers parameter. Administrators belong to the Administrators Active
Directory group.
For more information about the MSIDefaultInstallAllUsers parameter, refer ThinApp Package.ini
Parameters Reference Guide.
Force MSI Deployments for Each User or Each Machine
Regardless of the parameter values specified at build time, you can override MSI settings at deployment time.
For example, if you created the database with a value of 1 for the MSIDefaultInstallAllUsers parameter,
you can still force individual user deployments for Firefox 3.0 with the msiexec /i Firefox30.msi
ALLUSERS="" command.
If you use the ALLUSERS="" argument for the msiexec command, ThinApp extracts the captured executable
files to the %AppData% user directory.
Force MSI Deployments for Individual Users or for All Users on a Machine
(Optional) From the command line, type the msiexec /i <database>.msi ALLUSERS="" command to
force deployments for individual users.
(Optional) From the command line, type the msiexec /i <database>.msi ALLUSERS=1 command to
force deployments for all users on a machine.
Override the MSI Installation Directory
You can use the msiexec command to override the default MSI installation directory.
When ThinApp performs an individual machine MSI deployment, the default installation directory is the
localized equivalent of %ProgramFilesDir%\<inventory_name> (VMware ThinApp). If you install a Firefox
package for each machine, the package resides in %ProgramFilesDir%\Mozilla Firefox (VMware ThinApp).
When ThinApp performs an MSI deployment for individual users, the default installation directory is
%AppData%\<inventory_name> (VMware ThinApp).
In both cases, you can override the installation directory by passing an INSTALLDIR property to the msiexec
command.
Override the MSI Installation Directory
From the command line, type the msiexec /i <database>.msi
INSTALLDIR=C:\<my_directory>\<my_package> command.