This article provides some of the feature considerations related to Universal Broker as well as a list of the Horizon features that have limited or no support.

Feature Considerations

  • In a pod fleet that contains both Horizon pods and Horizon Cloud pods, each end-user assignment you create must consist of VDI desktops from only one pod type. For example, you can create an assignment consisting of desktops that span multiple Horizon pods or an assignment consisting of desktops that span multiple Horizon Cloud pods. However, you cannot create an assignment consisting of desktops that span a mix of Horizon pods and Horizon Cloud pods.
  • Additional considerations apply if you have transitioned your tenant from a single-pod broker configuration to Universal Broker. See What's New in Your Tenant Environment After the Transition to Universal Broker.

Virtual Resources

For the brokering of virtual resources, this release of Universal Broker only supports Windows operating systems. Linux-based desktops are not supported.

This release does not support administrator-created shortcuts to desktops and applications.

Note: A specific user can receive at most one assigned desktop from a dedicated assignment brokered by Universal Broker, even if the assignment includes desktops from multiple pods.

Horizon HTML Access and Horizon Client for Chrome

End users can make requests for resources to the Universal Broker service by running Horizon HTML Access in a supported web browser or by running Horizon Client for Chrome 5.4 or later. If the Universal Broker service redirects the request to a Unified Access Gateway instance that uses a self-signed certificate, the client application displays an error message indicating that the certificate authority is invalid.

This behavior is according to design. To connect to the requested resource, the user can accept the self-signed certificate by following the prompts in the certificate error message.

Authentication Methods

This release of Universal Broker supports client user authentication through Windows user name and password, in UPN and NETBIOS formats.

Two-factor authentication through Radius or RSA is also supported.

  • If your environment contains only Horizon Cloud pods in Microsoft Azure, Universal Broker supports Radius authentication only.
  • If your environment contains only Horizon pods (based on Horizon Connection Server technology), Universal Broker supports both Radius and RSA SecurID authentication.
  • If you have a mixed environment containing both Horizon Cloud pods and Horizon pods, Universal Broker supports Radius authentication only.

The following user authentication and access methods are not supported:

  • Smart card
  • Certificate
  • SAML authentication (outside of integration with VMware Workspace ONE)
  • Log in as the current user
  • Anonymous access

Remote Desktop Features

The following features are not supported in this release of Universal Broker:

  • URL content redirection
  • Session collaboration

Other Features

The following features are also not supported in this release of Universal Broker:

  • Kiosk mode
  • Smart policies that require the identification of a user's location (for example, policies that pertain specifically to internal or external users)
  • Timing profile (for troubleshooting user sessions )
  • OPSWAT-based endpoint compliance checks