This list is a high-level of the steps when you are onboarding your very first pod to your Horizon Cloud tenant environment and that pod is an existing manually deployed Horizon pod. A manually deployed pod is one that you manually installed and configured using either on-premises capacity or using VMware Cloud on AWS capacity. After these onboarding steps are completed for your very first cloud-connected pod, the subscription license is applied to that onboarded Horizon pod and you can start using the cloud-hosted services that Horizon Cloud provides for that pod type, which include the Cloud Monitoring Service (CMS). At that point, you can also onboard additional pods.

The following diagram illustrates the overall flow.


Conceptual diagram of the four steps in onboarding a Horizon pod to the cloud control plane.

Before beginning this workflow, you must have already installed and configured your Horizon pod. For information about manually installing a Horizon pod that you can use with this Horizon Cloud release:

  • For manually installing pods using on-premises capacity, see the relevant installation information for the most recent version of VMware Horizon from the Horizon Documentation page.
  • For manually installing pods using VMware Cloud on AWS capacity, see the best practices guide for deploying Horizon pods on VMware Cloud on AWS, available from the Horizon on VMware Cloud on AWS product page.

You onboard an existing Horizon pod to the cloud for two primary use cases: to activate a subscription license for that pod and enable your use of those cloud-hosted services that Horizon Cloud provides for this type of pod, such as the Cloud Monitoring Service (CMS). The CMS is one of the central services provided in Horizon Cloud. CMS provides for visibility, health monitoring, and help desk services with cloud-connected pods. For a high-level description of the process of onboarding a pod to the cloud control plane, see Onboarding to Horizon Cloud for Microsoft Azure, Horizon On-Premises, and Horizon on VMware Cloud on AWS.

Caution: Complete all of the steps below to fully connect your first pod to Horizon Cloud before you start deploying the Horizon Cloud Connector with any subsequent manually installed pod you want to connect. Due to a known issue in this release, if you finish connecting more than one pod to the cloud using the Horizon Cloud Connector before you complete the Active Directory domain registration and Super Administrators role assignment step at least once, the Active Directory domain registration step will fail. At that point, you will have to unplug all but one of your cloud-connected Horizon pods before you can successfully complete the required Active Directory domain registration and Super Administrators role assignment step.
  1. Fulfill the prerequisites, which includes obtaining a Horizon subscription license, such as the Horizon universal license. See VMware Horizon Pods with Horizon Cloud - Requirements Checklist - Updated As Appropriate for Connecting Pods Starting From the July 2020 Service Release as well as the prerequisites section in Connect Horizon Cloud Service with an Existing Horizon Pod to Use Horizon Subscription Licenses or Cloud-Hosted Services or Both.
  2. Verify you meet the DNS, ports, and protocol requirements for connecting a Horizon pod with Horizon Cloud. See DNS, Ports, and Protocols Requirements When Using Horizon Cloud Connector and a Horizon Pod.
  3. If your environment requires use of a proxy server for the Horizon Cloud Connector virtual appliance to reach the Internet, obtain the required proxy settings so that you can specify them when you deploy the appliance's OVF template.
    Important: If you plan to use Universal Broker with Horizon Cloud Connector 1.5, and require using proxy settings, you must configure those proxy settings when you deploy the OVF template. Due to a known limitation, the Universal Broker will not pick up changes to proxy settings made in the Horizon Cloud Connector appliance after the initial deployment process.

    Due to a known issue, the system is not honoring any no-proxy host configuration that you specified in the initial OVF template deployment. To use a no-proxy host configuration with the Horizon Cloud Connector appliance, you must configure it after the initial deployment process. See Modifying Proxy Settings for Horizon Cloud Connector 1.5 or Earlier for more details.

  4. Optionally log in to the Horizon Cloud tenant portal and configure additional administrators for your tenant environment.
    Tip: Even though you can complete the next steps to onboard the pod solely using the My VMware account that is the one initially associated with your tenant environment, it is prudent to configure additional administrators at the start of this process. If only a single My VMware account is associated with your tenant account and you lose access to the credentials, delays might occur because you'll have to open a service request with VMware to associate a new My VMware account with the tenant account. To prevent such delays, log in to the tenant portal at cloud.horizon.vmware.com with the initially associated My VMware account and then follow steps described in Add Administrators to Log in to Your Horizon Cloud Tenant Environment using the row in the General Setup section of the screen.
    Screenshot of the My VMware Accounts row in the General Setup section of the Getting Started wizard.
  5. Deploy the Horizon Cloud Connector virtual appliance into the pod's environment. Follow the OVA deployment steps described in Download and Deploy the Horizon Cloud Connector into the Pod's vSphere Environment.
  6. After the virtual appliance is powered up, enable SSH access to the virtual appliance to remotely run commands in the appliance's operating system. You must use your vSphere environment to launch the appliance's console, log in to the appliance's operating system using the root user that you set during deployment of the appliance, and run the appropriate commands to enable SSH. Follow the steps in Enable SSH Access to the Horizon Cloud Connector Prior to Pairing it with Your Horizon Connection Server.
    Note: Those steps to enable SSH are used for the time when the pod is not yet successfully paired with Horizon Cloud. After the pod is successfully paired with Horizon Cloud, then you will be able to use the browser-based Horizon Cloud Connector's configuration portal to enable and disable SSH access to the virtual appliance.
  7. If your environment requires use of a proxy and you did not specify proxy-related settings in the OVF deployment wizard, configure the proxy-related settings for the virtual appliance. See Modifying Proxy Settings for Horizon Cloud Connector 1.5 or Earlier for more details.
  8. If you want to access the browser-based Horizon Cloud Connector configuration portal using a fully-qualified domain name (FQDN) instead of using the Horizon Cloud Connector virtual appliance's IP address, create a forward and reverse lookup record in your DNS server that maps an FQDN to the virtual appliance's IP address.
  9. (Horizon Cloud Connector 1.6 or later) Verify the health of the pod's system components and services by opening an SSH session to the Horizon Cloud Connector virtual appliance and running the precheck.sh diagnostics script. See Verify the Horizon Pod and Virtual Appliance Are Ready to Be Paired for more details.
  10. Using either a mapped FQDN or the virtual appliance's IP address, log in to the browser-based Horizon Cloud Connector configuration portal and complete the onboarding steps that pair the connector with the pod's Connection Server. Follow the steps described in Complete Pairing the Horizon Pod with Horizon Cloud Using the Horizon Cloud Connector Configuration Portal.
    Tip: When the connector and Connection Server are successfully paired, the Horizon Cloud Connector configuration portal will display a Congratulations message. At this point, VMware will activate your subscription license. The activation is typically completed after 30 minutes but can take up to 48 hours in some cases. When the license is activated, you will see the message Connected to License Service in your pod's web-based console's Product Licensing & Usage screen.
    Screenshot of the Connected to License Service message in your standard Horizon screen.
  11. Depending on your team standard practices and environment, optionally configure the Horizon Cloud Connector virtual appliance in areas such as configuring a CA-signed certificate and setting a password expiry for the appliance's root user. See the topic .
  12. Complete the Active Directory domain registration workflow within the Horizon Cloud administrative console, named Horizon Cloud Administration Console, or console for short. See the topic Typical Administrative and Maintenance Tasks You Perform on the Horizon Cloud Connector After the Horizon Pod is Paired with Horizon Cloud in the Administration Guide.
    Tip: Completing the Active Directory domain registration workflow enables you to take advantage of all of the cloud-hosted services, such as the Cloud Monitoring Service (CMS). Until the pod's Active directory domain is registered with your tenant environment, the console's screens in which the CMS's monitoring data gets displayed are inaccessible.
  13. Give the Horizon Cloud Super Administrators role to an Active Directory group that includes that domain-join account as a member. See the topic Assign Horizon Cloud Administrative Roles to Active Directory Groups in the Administration Guide.

You can find in-depth details on how to accomplish each workflow step in the topics that are linked from each step above or in the companion guide. See the Horizon Cloud Administration Guide.