
VMware ThinApp
R E V I E W E R ’ S G U I D E / 1 3
Recommendations
Integrate the delivery of packages, which can be large .exe or .msi files, with your existing organizational
process. An existing process, such as Active Directory publishing via Group Policy, will have an already
established support structure and administration workflow. You can use Group Policy to deploy software to
groups, OU’s, or individuals. See the following KB article for details: http://support.microsoft.com/kb/324750
Benefits
Once the application package is delivered, application performance and availability is not subject to network or
storage dependencies.
Application Registration
The process of application registration integrates the virtualized application packages with the desktop
operating system. The process of registering applications will take into account the access control mechanisms
that allow administrators to restrict usage to specified Active Directory groups providing end users role-based
access to virtualized applications. Application registration is not mandatory, ThinApp packages will launch
and execute without registration. However, end users and administrators can benefit from the integration of
virtualized applications into the desktop because of the following:
• Creation of Windows Shortcuts on the Start Menu and Desktop for the applications
• Creation of File Type Associations, Protocols, and Object Types to launch virtualized applications
• Creation of Application Entries in the Add/Remove Programs Control Panel applet
VMware ThinApp allows IT organizations to determine whether to use streaming or deployed execution mode
or to adopt a hybrid approach that lets them manage a standard set of applications centrally while distributing
others in deployed mode. The same virtualized application packages can be used for either execution mode.
The application registration process performs the exact same function whether packages are local or remote.
As described later, MSI packages use ThinReg to automatically perform application registration with the MSI
installer. So the application registration entries are consistent regardless of the means use to perform the actual
registration or where the package resides.
Registration of virtualized applications to end users creates shortcuts on the desktop, file-type, protocol, and
object type associations, and entries in the Add/Remove programs applet of the Control Panel. The Thinreg.exe
tool is a simple utility, which automates the registration process and can be run from any scripting mechanism
or command prompt. The ThinReg.exe can be local to the operating system, on a remote share. An example
would be placing the ThinReg tool in the netlogon share and calling it from a login script. Administrators can
run ThinReg against an entire directory of ThinApp packages by using an asterisk (*) as a wildcard character.
Role-Based Access to Applications
Since the registration process can enumerate which users have access to application packages, the process can
be run against an entire directory of application packages; however, it only registers the applications to which
the user is entitled. Administrators can use pre-made scripts that run based on group membership to only
register packages that are valid for a certain group or for individuals. Two common methods of implementation
using Active Directory are described briefly below.
Script-based Registration
Implementation of the Thinreg executable can be incorporated into an existing login script with standard
methods such as .bat, WSH, KIX, or vbScript. See example below:
%logonserver%\netlogon\thinreg.exe /Q \\company.com\applications\*.exe
Local Script via Registry Run Key or Active Directory GPO managed Login and Logout Script
IT organizations can choose to implement the application registration process locally on the workstations
Commenti su questo manuale