Your overall Horizon Cloud environment consists of the VMware-hosted cloud service, your provided capacity, and VMware software deployed into that capacity and connected to the cloud service. When the VMware software installed in that capacity is appropriately configured and connected to the cloud service, that configured entity is now a cloud-connected pod. For such cloud-connected pods, you can use the Horizon Cloud Administration Console for visibility, health monitoring, and help desk services with those pods.
For an overall introduction to Horizon Cloud, see the Deployment guide for this service level.
To perform administrative tasks in the environment, you use the cloud-based Administration Console. This user interface provides an integrated view and centralized access to manage virtual desktops and applications for delivery to your end users. The Administration Console works in an industry-standard Web browser. For the list of supported Web browser types and versions, see the Release Notes.
Depending on the type of capacity you have access to, you can use the Horizon Cloud Administration Console for an automated pod deployment into that capacity and configure that pod for connection to Horizon Cloud. For some types of pods, even though they cannot be automatically deployed and configured, you can still connect the Administration Console to those pods that already exist, after performing some required connection steps.
When you are expecting to see a feature in the Administration Console and do not see it, contact your VMware account representative to verify whether your license entitles your use of that feature.
Before you can perform administrative tasks on a Horizon Cloud pod, you must:
- Connect your first pod to Horizon Cloud. For details, see the Getting Started guide for this service level.
- Register at least one Active Directory domain and grant the Super Administrator role to at least one of your Active Directory groups.
Registering the domain involves providing both:
Note: In this release, the domain-join account is used by system operations primarily with pods in Microsoft Azure. Cloud-connected Horizon 7 pods do not make use of the domain-join account that you specify in the Active Directory domain registration steps. However, even when you have only cloud-connected Horizon 7 pods for your environment, it is prudent to complete the domain-join account step to ensure that the subsequent prompt to assign the Super Administrators role is activated. Assigning that role to an Active Directory domain group is a required step for all types of cloud-connected pods.
- A primary domain-bind account and an auxiliary domain-bind account, used by Horizon Cloud to perform lookups in the Active Directory. By providing an auxiliary domain-bind account when you first register the domain, you prevent locking your administrator users out of the Administration Console if the primary bind account becomes inaccessible.
- A domain-join account, used by Horizon Cloud in pod operations that require joining virtual machines to the domain, such as when importing an image from the Microsoft Azure Marketplace, creating farm server instances, creating VDI desktop instances, and so on.
For the requirements on these domain-bind and domain-join accounts, see Service Accounts That Horizon Cloud Requires for Its Operations.
For details about the domain registration workflow , see Performing Your First Active Directory Domain Registration in the Horizon Cloud Environment.
Afterwards, a best practice is to follow the recommended actions displayed in the Getting Started wizard.
- Use the Unplug action in the Cloud Connector's cloud-pairing workflow to remove the connection between each of the cloud-connected pods until you are down to a single cloud-connected pod.
- Use the Administration Console to remove the failed registration, by following the steps in remove the failed Active Directory domain registration from Horizon Cloud.
- Complete the first Active Directory domain registration process, related to that pod.
- Re-run the Cloud Connector cloud-pairing workflow on the other pods.
After the first Active Directory domain is registered with Horizon Cloud for the pod's use, you can subsequently register additional Active Directory domains. Registering additional Active Directory domains provides for user-related management tasks that involve users in those domains, such as working with the help desk features. After the first Active Directory domain is registered, you can also configure additional auxiliary domain bind accounts and an auxiliary domain join account.