Requirements for Integrating Horizon Pod Federations with Omnissa Access

To integrate Horizon pod federations with Omnissa Access, make sure that you meet the requirements listed here.

• Omnissa Access supports the Cloud Pod Architecture feature for both applications and desktops.

• You can integrate a maximum of 10 pod federations with the Omnissa Access service.

• We recommend adding only one federation per virtual app collection. Therefore, create a separate virtual app collection for each federation.

• Up to 50 pods can be added per profile.

  • The 50 pods can be added as local pods or can be added to a Horizon Cloud Pod Architecture (CPA) federation, depending on how they are configured on Horizon.
  • If configured in federation, the 50 pods can be added to a single federation or up to a maximum of 10 federations, depending on how they are configured on Horizon.

• Deploy Horizon Connection Server instances on the default port 443.

• Verify that you have a DNS entry and an IP address that can be resolved during reverse lookup for each Horizon Connection Server instance in your environment. Omnissa Access requires reverse lookup for Horizon Connection Server, Security Server, and load balancer instances. If reverse lookup is not properly configured, the Omnissa Access integration with Horizon fails.

• The Omnissa Access Virtual App service must be able to reach all the Horizon Connection Server instances in the pod federation.

• You must create the pod federation, by initializing the Cloud Pod Architecture feature from one of the pods and joining all the other pods to the federation, before integrating with the Omnissa Access service. Global entitlements are replicated to pods when they join the federation.

  If you join or remove a pod from the pod federation after you integrate the pod federation with the Omnissa Access service, you must edit the pod federation details in the Omnissa Access console to add or remove the pod, save your changes, and sync again.

• In your Horizon environment, create global entitlements in the pod federation to entitle Active Directory users or groups to desktops and applications.

• (Optional) Create local entitlements on the pods, if required.

• In Horizon 7 versions prior to 7.13, to enable end users to launch desktops or applications in a Web browser, select the HTML Access option for the global entitlement.

  If you integrate Horizon 7.13 or later versions with Omnissa Access, end users always see the option in Intelligent Hub to launch applications and desktops in a browser. However, if HTML Access is not installed on the Horizon Connection servers, browser launch fails. For Horizon 7.13 and later versions, you must install HTML Access on the Horizon Connection servers. See the Horizon HTML Access documentation for information.

• When you configure the pod federation in the Omnissa Access console, make sure that the pod federation and its pods are contained in a single virtual apps collection. A pod federation cannot be part of multiple virtual apps collections.

For more information about configuring Horizon, see the Horizon documentation.