Keep these considerations in mind when you are using Horizon Cloud Connector.

  • When deploying the Horizon Cloud Connector appliance into a VMware SDDC environment, you must deploy it using vSphere Client or vSphere Web Client. Do not deploy the appliance directly into an ESXi host.
  • Use of IPv6 with the Horizon Cloud Connector virtual appliance is not supported.
  • Proxy SSL configuration is not supported during the deployment of the Horizon Cloud Connector virtual appliance.
  • Information about the static IP and proxy settings for the deployed Horizon Cloud Connector virtual appliance is saved in certain container files. When you want to change those settings on the virtual appliance, you must connect to the virtual appliance and edit those container files. If you change the static IP address for the deployed virtual appliance, you must edit the appropriate container file in the virtual appliance's operating system and run a command to ensure that the new IP address is shared with all the pod's components that depend upon the virtual appliance. See Update the Static IP for the Horizon Cloud Connector Virtual Appliance.
  • Before deleting the Horizon Cloud Connector virtual appliance from its deployed environment, point your browser to the Horizon Cloud Connector appliance's IP address and use the Unplug action to remove the connection between the pod and Horizon Cloud.
  • Using a separate vdmadmin account for the Horizon Cloud Connector paired with the Horizon pod is a best practice. Using a separate vdmadmin account avoids configurations being overridden between cloud and on-premises management. Using separate accounts also provides easier auditing for the cloud-based operations.
  • The connection between the Horizon Cloud Connector and Horizon Cloud uses outbound Internet port 443. For all the connector's required DNS, ports, and protocols, see DNS, Ports, and Protocols Requirements When Using Horizon Cloud Connector and a Horizon Pod.
  • You set the password for the root user of the Horizon Cloud Connector virtual appliance during deployment. By default, this password does not expire. However, based on your organization's security policy, you might want to periodically update that root password by setting an expiry policy for that root user. For steps, see Set a Password Expiry Policy for the Horizon Cloud Connector Root User.
  • If your Connection Server is using self-signed certificates and you then replace those self-signed certificates after pairing the pod with Horizon Cloud, you must log in to the Horizon Cloud Connector interface and use the Reconfigure workflow to perform the certificate validation steps again with the new self-signed certificate. When you log in to the Horizon Cloud Connector interface, you can click Reconfigure and complete the wizard steps to verify communication using the new self-signed certificate from the Connection Server.

    Similarly, upgrading your Connection Server might result in changes to self-signed certificates. To ensure validation of the new certificates, perform the Reconfigure workflow for the Horizon Cloud Connector after upgrading your Connection Server.

  • If you added an entry to the /etc/hosts file to resolve the IP address of the Connection Server, you must restart the hze-core and csms services. Use the following commands:
     systemctl restart hze-core
     systemctl restart csms
  • To ensure that the Horizon Cloud Connector virtual appliance authenticates correctly with Horizon Cloud and the required Connection Server instances, you must synchronize the virtual appliance's clock with an NTP server. For more information, see Synchronize the Horizon Cloud Connector Virtual Appliance with an NTP Server.
  • If you encounter connectivity issues with the Horizon Cloud Connector configuration portal, see the troubleshooting information in VMware Knowledge Base (KB) article VMware Knowledge Base (KB) article 79859.

Old, Deprecated Versions

New deployments of Horizon Cloud Connector are supported using versions N, N-1, N-2 where N is the latest Horizon Cloud Connector version. Prior versions are deprecated for use. Existing deployments are expected to update to the same versions. The deprecated version 1.5 had the following considerations in addition to the ones listed in the previous section. This list will be deleted from this page at the next release of Horizon Cloud Connector. For the numeric of the latest version, see the Release Notes.

  • Due to a known limitation, any no-proxy host configuration that you specify when deploying the OVF template is not honored by Horizon Cloud Connector 1.5 or earlier. To configure a no-proxy host configuration, you must change a configuration file in the appliance after it is deployed. For details, see VMware Knowledge Base article 76663. This limitation does not apply to Horizon Cloud Connector 1.6 or later.
  • If you plan to use the pod with Universal Broker and Horizon Cloud Connector 1.5, and your environment requires using proxy settings, you must configure those proxy settings when you deploy the OVF template. Due to a known limitation, Universal Broker will not honor any modifications made to proxy settings after deployment. Since you can only configure no-proxy hosts after deployment, this limitation means that the use of no-proxy hosts with Universal Broker is not supported by Horizon Cloud Connector 1.5. This limitation does not apply when you use Universal Broker with Horizon Cloud Connector 1.6 or later.