The process of integrating Omnissa Access with Horizon Cloud Service on Microsoft Azure with Single-Pod Broker or Horizon Cloud Service on IBM Cloud includes creating one or more virtual apps collections in the Omnissa Access console and syncing Horizon Cloud assignments to Omnissa Access using the Omnissa Access connector. You must also configure SAML authentication to enable trust between the Horizon Cloud tenant and Omnissa Access.
Important: Only Omnissa Access connector versions 22.05 and later support integration with Horizon Cloud Service on Microsoft Azure with Single-Pod Broker and Horizon Cloud Service on IBM Cloud environments. This documentation is based on the latest version of the connector.
Desktop and application pools are configured in the Horizon Cloud environment. You also set user and group entitlements in the Horizon Cloud tenant, not in the Omnissa Access service. You must sync these users and groups to the Omnissa Access service from Active Directory before integrating Omnissa Access with your Horizon Cloud tenant.
To integrate Horizon Cloud with Omnissa Access, you create one or more virtual apps collections in the Omnissa Access console. The virtual apps collections contain the configuration information for the Horizon Cloud tenants as well as sync settings.
You can set up a sync schedule for each virtual apps collection to regularly sync assignments from the Horizon Cloud tenants to the Omnissa Access service.
After you integrate the Horizon Cloud tenants with Omnissa Access and sync the virtual apps collection, you can see the Horizon desktops and applications in the Omnissa Access console. You can also view user and group entitlements.
End users can launch their assigned desktops and applications from the Omnissa Intelligent Hub app or portal. These desktops and applications can be accessed in a browser or in the Omnissa Horizon® Client™.
Was deze pagina nuttig?