When onboarding a Horizon pod to use the first-gen Horizon control plane services, ensure you have the following items in place before you deploy the Horizon Cloud Connector appliance and run the onboarding wizard.
Important Use this page solely when you have access to a first-gen tenant environment in the first-gen control plane. As described in KB-92424, the first-gen control plane has reached end of availability (EOA). See that article for details.
Confirm These Things
-
Verify you have met the prerequisites described in Horizon 8 Pods with First-Generation Horizon Cloud Control Plane - Requirements Checklist.
-
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 Customer Connect account at https://customerconnect.omnissa.com and that account has a Horizon subscription license associated with it. This account is needed to run the Horizon Cloud Connector onboarding workflow to pair the pod with your specific service tenant, and for logging in to the cloud-based administrative console to perform administrative tasks, including adding additional administrators to your tenant.
-
Your account has been authorized to log in to your service tenant. You might be the initial subscriber to the service or the initial subscriber has added your account as an administrator to the tenant or an existing administrator in your organization added your account as an administrator to the tenant. All those cases would make for an authorized account. To see if your Customer Connect account is authorized to log in to your service tenant, go to https://cloud.horizon.omnissa.com and enter those account credentials. If the system logs you in, then your account is authorized. If not, you will have to ask one of your organization's tenant administrators to log in to the service tenant and add you or file a non-technical support request in Customer Connect using the steps in KB article 2006985 to request your addition to your organization's existing tenant record.
-
The Horizon Cloud Connector binary component must be downloaded from customerconnect.omnissa.com. In Customer Connect Downloads area, locate the Horizon Service row and view its download components. Within that page you’ll see the Horizon Cloud Connector row and can click on its Go to Downloads to obtain the latest version of the Horizon Cloud Connector.
-
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.
- Decide on a strong root password for the virtual appliance. For all-in-SDDC deployments, the OVF deployment wizard will prompt for a password that contains a minimum of eight characters with one capital, one numeric, and one special character. For federated deployments, the password must adhere to the requirements of the native cloud platform.
Important: All-in-SDDC deployments will involve using the OVF deployment wizard to deploy the appliance into the vSphere-based SDDC. 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 this prerequisite, in addition to the ones listed above:
- The Horizon 8 Connection Server instance with which you will be pairing the Horizon Cloud Connector must be running a version of Horizon 8 that is within General Support, and no earlier than Horizon 8 version 2006. For the Horizon 8 versions that are within General Support, refer to Omnissa Lifecycle Matrix.
Tip Even though technically you might be able to 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.
Was this page helpful?