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
40 VMware, Inc.
Table 3-1. Optional thinreg.exe Parameters
Parameter Purpose Sample Usage
/a, /allusers Registers a package for all users.
If an unauthorized user attempts to run
the application, a message informs the
user that he or she cannot run the
application.
thinreg.exe /a
"\\<server>\<share>\Microsoft Office
2007 Word.exe"
/q, /quiet Prevents the display of an error message
for an unrecognized command-line
parameter.
thinreg.exe /q <unknown_option>
/u, /unregister,
/uninstall
Unregisters a package.
This command removes the software from
the Add/Remove Programs control panel
applet.
Unregister Microsoft Word for the current user.
thinreg.exe /u
"\\<server>\<share>\Microsoft Office
2007 Word.exe"
Unregister all Microsoft Office applications for
the current user and remove the Add/Remove
Programs entry.
thinreg.exe /u
"\\server\share\Microsoft Office *.exe"
If a user registers the package with the /a
parameter, you must use the /a parameter when
unregistering the package.
thinreg.exe /u /a *.exe
/r, /reregister Reregisters a package.
Under typical circumstances, the
thinreg.exe utility can detect whether a
package is already registered and skips it.
The /r option forces the thinreg.exe
utility to reregister the package.
thinreg.exe /r
"\\<server>\<share>\Microsoft Office
2007 Word.exe"
If a user registers the package with the /a
parameter, you must use the /a when
reregistering the package.
thinreg.exe /r /a *.exe
/k,
/keepunauthorized,
/keep
Prevents the removal of registration
information even if you are no longer
authorized to access an application
package.
Without this option, the thinreg.exe
utility removes the registration
information for that package if it detects
you are no longer authorized to access the
package.
ThinApp stores authorization information
in the PermittedGroups parameter of the
Package.ini file.
thinreg.exe /k
"\\<server>\<share>\Microsoft Office
2007 Word.exe"
/noarp Prevents the creation of an entry in the
Add/Remove Programs control panel
applet.
thinreg.exe /q /noarp
"\\<server>\<share>\Microsoft Office
2007 Word.exe"
/norelaunch Starts the thinreg.exe
utility on
Microsoft Vista without elevated
privileges. Standard users can start the
utility without a user account control
(UAC) pop-up window.
When the thinreg.exe utility detects a
need for more privileges, such as the
privileges required for the /allusers
parameter, the utility restarts itself as a
privileged process and generates a UAC
pop-up window. The /norelaunch
option blocks this restart process and
causes the registration to fail.
thinreg.exe /q /norelaunch
"\\<server>\<share>\Microsoft Office
2007 Word.exe"










