The Horizon Universal Console's Capacity page displays the current state of cloud-connected Horizon pods (based on Horizon Connection Server technology). In this release, a Horizon pod can be in either monitored or managed state. Only when the pod is in managed state can you use that pod's resources in multi-cloud assignments (MCAs).

Monitored State

Monitored state is the default state of a Horizon pod after you first connect the pod to your Horizon Cloud environment. The following list describes the features available for a pod in monitored state:

Managed State

If a monitored pod meets certain requirements, you can change the Horizon pod's state to the managed state. See Use the Horizon Universal Console to Change a Cloud-Connected Horizon Pod to Managed State.

A managed pod offers all the features available for a monitored pod. In addition, you can create multi-cloud assignments that use resources from a managed pod, and manage those multi-cloud assignments using the Horizon Universal Console. For more information, see Managing Multi-Cloud Assignments in Your Horizon Cloud Tenant Environment.

Use the Horizon Universal Console to Change a Cloud-Connected Horizon Pod to Managed State

For the Horizon pods in your tenant's fleet, after you save the Universal Broker settings, you can change those pods from monitored to managed state. Changing a pod to managed state lets you add assignments from that pod to a Universal Broker environment. Also, then you can leverage the features of Image Management Service (IMS), an additional service provided by Horizon Cloud.

You run the change-state workflow from the Horizon Universal Console's Capacity page. You must first save the Universal Broker settings using the console's Broker page before running the change-state workflow from the Capacity page.

Prerequisites

Procedure

  1. Click Settings > Capacity. Select the Pods tab if it is not already selected.
  2. Select the pod in the list and then click More > Change State.
    The console displays the window for the change-state workflow.
  3. In the change-state workflow's window, configure the pod's site association.
    • To associate the pod with a new site, select New and enter the name of the new site.
    • To associate the pod with an existing site, select Existing and select a site from the drop-down menu.
  4. (Optional) If you want to support use of this pod by end users on external networks or use two-factor authentication, then enable the toggle to indicate that, and specify the external FQDN (fully-qualified domain name). The FQDN is typically defined as follows:
    • When the pod has multiple external Unified Access Gateway instances, specify the address of the local load balancer as the pod's FQDN.
    • When the pod has only one external Unified Access Gateway instance, specify the address of that Unified Access Gateway instance as the pod's FQDN.
  5. (Optional) When the pod also has internal Unified Access Gateway instances, enable the toggle to indicate that you will have internal end users accessing their desktops on your internal network, and then specify the internal FQDN.
    After enabling the toggle, a field will display to provide the pod's internal FQDN.
    • When the pod has multiple internal Unified Access Gateway instances, specify the address of the local load balancer used by those instances as the pod's internal FQDN.
    • When the pod has only one internal Unified Access Gateway instance, specify the address of that Unified Access Gateway instance as the pod's internal FQDN.
  6. Click Save.

Results

The pod undergoes a validation process to ensure that it meets all the necessary configurations described in System Requirements for Universal Broker. If the pod passes the validation process, it is enabled for participation in the Universal Broker environment and the Capacity page displays the pod's state as Managed.
Note: If the pod does not pass the validation process, a message appears with details describing the system configuration that is missing (for example, the Universal Broker plugin is not installed). Perform the necessary actions to correct the pod's configuration before you reattempt to change the pod to managed state.

What to do next

If your pod has internal Unified Access Gateway instances and you configured Universal Broker to use two-factor authentication, but you want to bypass that two-factor authentication for your internal end users, then proceed to define internal network ranges so that Universal Broker will identify those as internal connections for the purpose of skipping the two-factor authentication for them. See Define Internal Network Ranges for Universal Broker.

Horizon Pods - Change a Pod to Monitored State

To change a Horizon pod (based on Horizon Connection Server technology) from managed to monitored state, you must first disconnect the pod and then redeploy it again to Horizon Cloud. After you redeploy the pod, it appears on the Capacity page in monitored state.

Procedure

  1. Remove the pod from any desktop assignments that include that pod. For detailed instructions, see Edit a Multi-Cloud Assignment in Your Horizon Cloud Tenant Environment.
  2. Disconnect the pod from Horizon Cloud. For detailed instructions, see Removing Cloud-Connected Horizon Pods from Use with Horizon Cloud.
    The pod is disconnected from Horizon Cloud, and the pod's name disappears from the Capacity page.
  3. Repeat the procedure to onboard the pod to Horizon Cloud. For more information, see First-Gen Tenants - About the First-Gen Horizon Universal Console Capacity Page and Adding Pods to Your Horizon Cloud Pod Fleet.

Results

The onboarded pod appears on the Capacity page in monitored state.