Using Software Delivery › Delivering Virtual Applications › How Virtual Application Deployment Works › Preparing a Target Computer for Deployment of a VMware ThinApp Virtual Application

Preparing a Target Computer for Deployment of a VMware ThinApp Virtual Application

Before you can deploy a VMware ThinApp virtual application package to a target computer, you need to verify that the target computer is ready for the virtual application. The following sections explain the preparation of the target computers.

Dependencies—For virtual application packages created from a VMware ThinApp image, certain dependencies are required. The following table identifies these dependencies based on the type of virtual application package you want to deploy.

ThinApp virtual application Staging packages for the server do not need any prerequisites. However, the Standalone and Streaming packages that deploy ThinApp packages to target computers call the ThinReg.exe utility. This program provides the end user with easy access to the virtual application.

Important! The ThinReg.exe utility must be found in the PATH environment on the target computer. If it is not, the deployment of the virtual application package on the target computer will fail.

You can use your own local procedures to make the ThinReg.exe utility available on the target computers, or you can use CA ITCM to create a software delivery package for the ThinReg.exe utility. This infrastructure package can then be imported into the Software Package Library using existing methods for importing packages. For more information on creating infrastructure packages, see the description in Virtual Application Infrastructure Package Templates.

Note: You can deploy virtual application packages on target scalability servers and target computers running the Windows operating system, but not UNIX or Linux operating systems.

Authorization—The end user on the target computer needs authorization to access a virtual application, which is located on a network drive on the scalability server. Authorization can be achieved by a trusted connection between the target computer and the server. If a trusted connection does not exist, the end user will be prompted for a user name and password.