User`s guide
VMware ThinApp Reviewer’s Guide
REVIEWER’S GUIDE / 35
to use the package until the Horizon Agent is able to check with the service for changed entitlement. The
default length of time that a user can launch a ThinApp package and not reconnect to the network is thirty
days. If the user does not reconnect to the network, the ThinApp package expires, and they cannot launch it.
Procedures to Deploy and Manage ThinApp Packages in Horizon Application Manager
To deploy and manage ThinApp packages in Horizon Application Manager, you must:
Enabling a ThinApp Package for Horizon
ThinApp package for Horizon during the Setup Capture process. You must capture and build the package in
Enabling a ThinApp
Package for Use in Horizon Application Manager
Enabling ThinApp
Packages Created Prior to ThinApp 4.7 for Horizon Application Manager
.
Creating the ThinApp Repository (Windows Application Share) for Horizon Application Manager
The Horizon Connector communicates to the Horizon Service metadata about the ThinApp packages on the file
share.
file share for the ThinApp packages and place the packages there.
Installing and
Configuring Horizon Connector guide and the Horizon Administration Help.
Create a folder structure for the applications on the file share as follows:
\\Server\sharename\virt_appname1
\\Server\sharename\virt_appname2
The subfolder name for the virtual application does not have any particular restrictions, so you can customize
as you wish.
bin
EXE-
based virtualized applications. You do not need to copy the MSI packages from the bin directories. However,
for possible future use, you can copy the MSI files, also. No errors will occur if you include the MSI packages on
Note:
desktops and application metadata can flow freely to the connector.