5.0

Managing ThinApp Applications in
View Administrator 13
You can use View Administrator to distribute and manage applications packaged with VMware ThinApp™.
Managing ThinApp applications in View Administrator involves capturing and storing application packages,
adding ThinApp applications to View Administrator, and assigning ThinApp applications to desktops and
pools.
You must have a license to use the ThinApp management feature in View Administrator.
This chapter includes the following topics:
n
“View Requirements for ThinApp Applications,” on page 223
n
“Capturing and Storing Application Packages,” on page 224
n
“Assigning ThinApp Applications to Desktops and Pools,” on page 227
n
“Maintaining ThinApp Applications in View Administrator,” on page 234
n
“Monitoring and Troubleshooting ThinApp Applications in View Administrator,” on page 237
n
“ThinApp Configuration Example,” on page 240
View Requirements for ThinApp Applications
When capturing and storing ThinApp applications that will be distributed to View desktops in View
Administrator, you must meet certain requirements.
n
You must package your applications as Microsoft Installation (MSI) packages.
n
You must use ThinApp version 4.6 or later to create or repackage the MSI packages.
n
You must store the MSI packages on a Windows network share that resides in an Active Directory domain
that it accessible to your View Connection Server host and View desktops. The file server must support
authentication and file permissions that are based on computer accounts.
n
You must configure the file and sharing permissions on the network share that hosts the MSI packages to
give Read access to the built-in Active Directory group Domain Computers. If you plan to distribute
ThinApp applications to domain controllers, you must also give Read access to the built-in Active
Directory group Domain Controllers.
n
To allow users access to streaming ThinApp application packages, you must set the NTFS permission of
the network share that hosts the ThinApp packages to Read&Execute for users.
n
Make sure that a disjoint namespace does not prevent domain member computers from accessing the
network share that hosts the MSI packages. A disjoint namespace occurs when an Active Directory domain
name is different from the DNS namespace that is used by machines in that domain. See VMware
Knowledge Base (KB) article 1023309 for more information.
VMware, Inc.
223