This article explains how to add your session desktop pools and remote application pools from cloud-managed Horizon pods to a Universal Broker environment. These pools, also known as RDSH pools, consist of resources provisioned by Microsoft Remote Desktop Services (RDS) hosts within a single Horizon pod. End users can open sessions by connecting to the Universal Broker FQDN, and Universal Broker serves as the connection broker for these sessions.

An RDSH pool consists of desktops or applications provisioned by Microsoft Remote Desktop Services (RDS) hosts within a single Horizon pod. When you add RDSH pools to your Universal Broker environment, the pools become read-only assignments in Horizon Universal Console. For more information, see Horizon Pods - Working with RDSH Assignments in Horizon Universal Console.

Prerequisites

Verify that you have completed the following prerequisite steps.

Procedure

  1. Open Horizon Console (the administrator console for Horizon pods) for the pod containing the RDSH desktop or application pool that you want to configure.
    For details on how to use Horizon Console, see the VMware Horizon Documentation.
  2. In Horizon Console, open the wizard for configuring an RDSH desktop or application pool.
  3. In the configuration wizard, enable the Cloud Brokered option for the pool.
    Universal Broker only recognizes RDSH desktop and application pools marked as Cloud Brokered.
    • For an RDSH desktop pool, the Cloud Brokered option appears in the section of the wizard that allows you to configure the pool settings.
    • For an application pool, the Cloud Brokered option appears in the section of the wizard that allows you to add applications.
  4. To save your changes to the pool, follow the prompts in the configuration wizard.
    Allow up to 10 minutes for the pool's configuration information to synchronize with the Universal Broker service.
  5. In Horizon Universal Console, navigate to the assignments page for RDSH desktops and applications from pods in a VMware SDDC. Verify that the pool that you configured as Cloud Brokered appears as a listed assignment on the page.

Results

Entitled users can now access the pool's desktops or applications by connecting to the Universal Broker FQDN.

The pool's configuration information is automatically synchronized to the Universal Broker service at the following times.

  • When the pool is created in Horizon Console.
  • When the pool's configuration is modified in Horizon Console.
  • When the pool is deleted in Horizon Console.

For more information, see Horizon Pods - Working with RDSH Assignments in Horizon Universal Console.

Horizon Pods - Working with RDSH Assignments in Horizon Universal Console

When you prepare an RDSH desktop or application pool in a cloud-managed Horizon pod with appropriate configuration, the pool becomes available as an RDSH assignment in your tenant environment, and you can view and monitor these assignments with the Horizon Universal Console.

For information about how to add RDSH assignments to your tenant, see Horizon Pods - Configure RDSH Desktops and Applications for a Universal Broker Environment.

Note: The following feature limitations and considerations apply to cloud-brokered RDSH desktop and application pools from Horizon pods (based on Horizon Connection Server technology).
  • The RDSH pools appear as read-only RDSH assignments in Horizon Universal Console. You cannot make configuration changes to these assignments using Horizon Universal Console.
  • To modify the configurations of RDSH assignments, you must use Horizon Console (the administrator console for Horizon pods).
  • RDSH assignments do not support the search feature of Horizon Universal Console. When you use this feature to search for a user or virtual machine (VM), RDSH assignments from Horizon pods are not included in the scope of the search.

To view details about a cloud-brokered RDSH assignment in Horizon Universal Console, navigate to the assignments page for RDSH desktops and applications from pods in a VMware SDDC. If your environment has multiple pods with cloud-brokered RDSH assignments, select a specific pod using the menu at the top of the page.

Clicking the name of an assignment listed on the page opens that assignment's details page consisting of three tabs: Summary, Sessions, and Entitlements. You can view different types of information on each tab. The information displayed on the tabs reflects the current configuration of the RDSH pool as defined in Horizon Console.

Summary Tab

On the Summary tab of the assignment details page, you can view general information about the status and configuration of the RDSH pool, such as information about its underlying farm. You can also perform the following actions.

Action Description
Sync Now

Manually synchronizes the pool's configuration information to the Universal Broker service. You can perform a manual synchronization to remedy problems that occur when the automatic synchronization fails or is delayed.

For example, perform a manual synchronization in the following cases:

  • When Horizon Universal Console displays a notification about a failure in automatic synchronization.
  • When entitled users cannot see or access the pool resources after connecting to the Universal Broker FQDN.
  • When a Horizon pod had preexisting RDSH desktop or application pools configured in Horizon Console before you paired the pod with Horizon Cloud Connector and changed the pod to managed state. Because the preexisting RDSH pools are not automatically synchronized with the Universal Broker service, you must manually synchronize each individual pool.

For details about when automatic synchronization typically occurs, see Horizon Pods - Configure RDSH Desktops and Applications for a Universal Broker Environment.

Launch Horizon Console

Opens Horizon Console for the pod that is the source of the pool.

Note: If you deactivate the Cloud Brokered option for the pool in Horizon Console, the pool is no longer listed as an assignment in Horizon Universal Console and users can no longer access the RDSH assignment through the Universal Broker FQDN.

In some cases, the RDSH pool remains accessible through the Universal Broker FQDN even after the Cloud Brokered option is deactivated or the pool is deleted in Horizon Console. If you encounter this situation, contact VMware support to request removal of the RDSH pool from the Universal Broker service.

Sessions Tab

The Sessions tab of the assignment details page lists the user sessions that are currently open on the pool.

Entitlements Tab

The Entitlements tab of the assignment details page lists the users who are entitled to access the pool's resources, as configured in Horizon Console.

User Activity Tab

The User Activity tab of the assignment details page displays activity in the assignment due to user actions, such as logging on and logging off sessions provided by the assignment.

To export the displayed information as a report file, click the Export feature and then follow the on-screen prompts.