To use Omnissa Access to distribute and manage applications packaged with ThinApp, you must have a ThinApp repository that contains the ThinApp packages, point to that repository, and sync the packages. After the sync process is finished, the ThinApp packages are available in your Omnissa Access catalog and you can entitle them to your Omnissa Access users and groups.
The ThinApp packages must be enabled with the appropriate options to be managed by Omnissa Access.
The ThinApp repository must be a network share that is accessible to the Virtual App service, a component of the Omnissa Access Omnissa Access connector, using a Uniform Naming Convention (UNC) path. The Virtual App service synchronizes with this network share regularly to obtain the ThinApp package metadata that Omnissa Access requires to distribute and manage the packages.
Omnissa Access supports Server Message Block (SMB) file shares.
For more information about requirements, see Requirements for ThinApp Integration with Omnissa Access.
Was this page helpful?