Establishing File Type Associations with the thinreg.exe Utility
If you create executable files instead of MSI files during the capture process, you must run the thinreg.exe utility to open files, such as a .doc document or an .html page. For example, if you click a URL in an email message, ThinApp must be set to start Firefox. You do not have to run the thinreg.exe utility for MSI files because MSI files start the utility during the application installation.
The thinreg.exe utility creates the Start menu and desktop shortcuts, sets up file type associations, adds deinstallation information to the system control panel, and unregisters previously registered packages. The utility enables you to see the control panel extensions for applications, such as Quicktime or the mail control panel applet for Microsoft Outlook 2007. When you right-click a file, such as a .doc file, the thinreg.exe utility enables you to see the same menu options for a .doc file in a native environment.
If an application runs SMTP or HTTP protocols, such as an email link on a Web page that needs to open Microsoft Outlook 2007, the thinreg.exe utility starts available virtual applications that can handle those protocols. If virtual applications are not available, the thinreg.exe utility starts native applications that can handle those protocols.
The default location of the utility is C:\Program Files\VMware\VMware ThinApp.
Application Sync Effect on the thinreg.exe Utility
The Application Sync utility affects the thinreg.exe utility during the update process.
If you add, modify, or remove executable files, the thinreg.exe utility reregisters the file type associations, shortcuts, and icons.
If you install protocols, MIME types, control panel applets, and templates other than executable files, the thinreg.exe utility reregisters these elements.
Run the thinreg.exe Utility
This example of running the thinreg.exe utility provides some sample commands.
The package name in the thinreg.exe commands can appear in the following ways:
As a variation, you can use a wildcard specification, such as *.exe.
If the path or filename contains spaces, enclose the path in double quotation marks. The following command shows the use of double quotation marks.
thinreg.exe "\\DEPLOYSERVER\ThinApps\Microsoft Office Word 2007.exe"
For information about thinreg.exe parameters, see Optional thinreg.exe Parameters.
Run the thinreg.exe utility
1
2
thinreg.exe [<optional_parameters>] [<package1.exe>][<package2.exe>][<packages_by_wildcard>]
If the server name is DEPLOYSERVER and the share is ThinApps, use the following example to register Microsoft Word for the logged-in user.
ThinReg.exe "\\DEPLOYSERVER\ThinApps\Microsoft Office 2007 Word.exe"
Use the following example to register all Microsoft Office applications in the specified directory for the logged-in user.
ThinReg.exe "\\DEPLOYSERVER\ThinApps\Microsoft Office *.exe"
Optional thinreg.exe Parameters
The thinreg.exe utility monitors the PermittedGroups setting in the Package.ini file, registering and un registering packages as needed. When the thinreg.exe utility registers a package for the current user, the utility creates only the shortcuts and file type associations that the current user is authorized for in the PermittedGroups setting. If this setting does not exist, the current user is authorized for all executable files.
When the thinreg.exe utility registers a package for all users with the /allusers parameter, ThinApp creates all shortcuts and file type associations regardless of the PermittedGroups setting. When you double-click a shortcut icon that you are not authorized for, you cannot run the application.
If the package name you want to register or unregister contains spaces, you must enclose it in double quotation marks.
For information about the PermittedGroups setting and support for Active Directory groups, see “PermittedGroups” parameter in ThinApp Package.ini Parameters Reference Guide.
Optional thinreg.exe Parameters lists optional parameters for the thinreg.exe utility. Any command that uses the /a parameter requires administrator rights.
/a, /allusers
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.
/u, /unregister, /uninstall
This command removes the software from the Add/Remove Programs control panel applet.
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.
/r, /reregister
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.
/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"
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"
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"