
VMware ThinApp
R E V I E W E R ’ S G U I D E / 1 4
instead of incorporating it into the login script. The Run key of the registry can call the Thinreg.exe file to
perform the necessary functions on login. Placing the Thinreg.exe in the Windows directory simplifies the
execution of the script and requires nothing more than the executable to function.
MSI-based Registration
Deployment of Virtualized Applications with Electronic Software Distribution (ESD) Tools and Active
Directory
Organizations can integrate the delivery of ThinApp packages run in deployed mode whether they are .EXE
or MSI based packages. These delivery mechanisms often have an already established support structure and
administration workflow. You can use native Active Directory based Group Policy to publish or assign MSI
packages to groups, OUs, or individuals. See the following knowledge base (KB) article for details: http://
support.microsoft.com/kb/324750
An organization with an established mechanism for deploying MSI files, such as Active Directory, can deploy
ThinApp MSI packages in the same manner that they would deploy native applications. The process of
registering applications to the desktop makes use of the ThinReg utility whether the package is deployed as
an .Exe based package or in an MSI wrapper. MSI-based packages are always ‘installed’ into the local operating
system. However, ThinApp MSI packages actually contain the EXE based package and the ThinReg utility. The
use of ThinApp MSI packages doesn’t actually install anything but rather puts the application registration
process into the MSI install. In summary, for organizations that use MSI-based ThinApp packages there will be
no need to make use of the ThinReg utility to perform application registration.
Deploying ThinApp Packages
The last step of the Setup Capture Wizard prompts the administrator for advanced configuration before
commencing ‘Build’ of the package. Once the build process has completed the completed ThinApp packages
are found in the ‘Bin’ folder of the project directory. If both an EXE and MSI package was created then
both types will be available. The packages contain all of the configuration information specified during the
Setup Capture process. To deploy the packages simply copy or distribute them to the appropriate locations.
Portability of these packages gives administrators and end users significant flexibility for distribution, use the
Active Directory authorization mechanism to secure these packages if necessary.
To utilize deployed mode execution
CopytheEXEorMSIbasedpackagetoalocalfilesystemorUSBdrive
NoteFortheMSIpackageyoumustdouble-clicktoinstallthepackage
Launchtheapplicationandtestfunctionality
To utilize streamed mode execution
CopytheEXEbasedpackagetoaremotefileshare
Dragashortcutfromthepackagetoyourdesktop
Launchtheapplicationandtestfunctionality
To utilize packages on multiple operating systems
CopytheEXEbasedpackagetoaWindowsXPWindowsVistaWindowsWindowsServer
PublishtheapplicationasaRemoteAppusingMicrosoftRemoteDesktopServices
PublishtheapplicationfromaCitrixXenApporPresentationServer
Launchtheapplicationsandtestfunctionality
Commenti su questo manuale