While setting up Horizon pods, ensure that you meet the requirements for the Workspace ONE Access integration.

  • Deploy Horizon Connection Servers on the default port 443 or on a custom port.
  • Verify that you have a DNS entry and an IP address that can be resolved during reverse lookup for each Horizon Connection Server in your setup. Workspace ONE Access requires reverse lookup for the Horizon Connection Servers, Horizon Security Server, and the load balancer. If reverse lookup is not properly configured, the Workspace ONE Access integration with Horizon fails.
  • Deploy and configure Horizon pools and desktops with entitlements set for Active Directory users and groups. Ensure that users have the correct entitlements.
  • While configuring desktop pools, ensure that in Remote Settings, you set the Automatically log off after disconnect option to 1 or 2 minutes instead of immediately.
  • Ensure that you create pools in the root folder of the Horizon server. If you create pools in a folder other than the root folder, Workspace ONE Access cannot query those Horizon pools and entitlements.
  • Extending the SAML metadata expiration period on the Horizon Connection Servers to 1 year is recommended. See Change the Expiration Period for Service Provider Metadata on View Connection Server for information.
  • If you integrate Horizon 7.13 or later versions with Workspace ONE 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 VMware Horizon HTML Access documentation for information.