To connect an existing Horizon pod with the current service release level for the purposes of using Horizon subscription licenses or cloud-hosted services with that pod, ensure you have the following items in place before you deploy the Horizon Cloud Connector appliance and running the onboarding wizard.

  • Verify you have met the prerequisites described in VMware Horizon Pods with Horizon Cloud - Requirements Checklist - Updated as Appropriate for Connecting Pods Starting from the October 2020 Service Release.
  • You have determined which of the pod's Connection Server instances you will pair with the Horizon Cloud Connector virtual appliance and you have the FQDN of that Connection Server instance. You can pair the Horizon Cloud Connector virtual appliance with only one of the pod's installed Connection Server instances at any given time.
  • You have determined which of the pod's administrator accounts you will specify when pairing the Connection Server with the Horizon Cloud Connector and that administrator account meets the requirements needed for pairing. This Active Directory user must have the Horizon predefined Administrators role on the root access group, as displayed in your pod's web-based console in Global Administrators View > Role Permissions > Administrators. In other words, the Active Directory user specified for the pod-onboarding process is a super user for that pod, as described in the Horizon documentation's Horizon Console Administration guide.
  • You have a valid My VMware account at https://my.vmware.com. This account is required to purchase a Horizon subscription license, for running the Horizon Cloud Connector onboarding workflow to pair the pod with the cloud service, and for logging in to the cloud-based administrative console to use the cloud-hosted services with that pod.
  • A Horizon subscription license is associated with that My VMware account.
  • You have the information from the welcome email that was sent to that My VMware account's associated email address, including the link for downloading the Horizon Cloud Connector OVA. If you do not have the email information, you can download the OVA by logging in to my.vmware.com using that My VMware account and navigating to the product downloads that are listed for that account.
  • If you are using the Microsoft Internet Explorer Web browser, verify that the compatibility mode is off. This setting enables viewing the Horizon Cloud Connector appliance onboarding user interface in that web browser.
  • Verify that you have met the DNS, ports, and protocols requirements.
  • Determine the static IP address that you will use for the Horizon Cloud Connector virtual appliance. You will need this IP address when you deploy the Horizon Cloud Connector appliance.
    Note: Do not use IPv6 with the Horizon Cloud Connector virtual appliance. IPv6 is not supported.
  • Verify you have the typical networking information that is appropriate for your environment to use when you deploy the Horizon Cloud Connector appliance in your pod's environment, such as your DNS search domain, DNS server IP address, default gateway address, and subnet mask.
    Note: Proxy SSL configuration is not supported for the self-signed certificate for the Horizon Cloud Connector virtual appliance.
  • (Horizon pods on premises or in VMware Cloud on AWS) Verify you have a strong root password for the Horizon Cloud Connector virtual appliance containing a minimum of eight characters with one capital, one numeric, and one special character.
    Important: When deploying the OVF template, you must specify a root password that meets the security standards of a strong password. However, due to a known limitation, the OVF deployment wizard continues to deploy the virtual appliance even if you specify a root password that does not contain a special character. In this case, the deployment succeeds but you will be blocked from logging in to the virtual appliance's operating system after deployment.

    To ensure your access to the virtual appliance after it is deployed, always specify a strong root password containing at least one special character as prompted by the OVF deployment wizard.

  • For the minimum use case of using Horizon subscription licenses with the Horizon pod, verify that you meet these prerequisites, in addition to the ones listed above:
    • The Connection Server instance with which you will be pairing the Horizon Cloud Connector must be running version 7.10 or later. Version 7.10 is the minimum version that can be paired with the cloud service.
      Tip: Even though technically you can pair a Horizon pod that is running versions older than the latest version, to obtain the most up-to-date cloud-hosted features with that pod, the pod's Connection Servers would best be running the most current software version. Only by using the most current combination of the Connection Server version and Horizon Cloud Connector version will you get access to the most up-to-date features of the cloud-hosted features beyond simply using a subscription license with that pod.