If your deployment uses load balancers to manage multiple Connection Server instances, an upgrade of the Connection Server infrastructure can be performed with zero down time.

Note: Before you can use the Horizon 6 version 6.2 feature for cloning a desktop pool, you must upgrade all Connection Server instances in a pod to Horizon 6 version 6.2 or later.

After you have performed a fresh install or upgraded all Connection Server instances to Horizon 7 version 7.2, you cannot downgrade the Connection Server instances to a version earlier than Horizon 7 version 7.2 because the keys used to protect LDAP data have changed.

To keep the possibility of downgrading Connection Server instances while planning an upgrade to Horizon 7 version 7.2, you must backup the Connection Server instances before starting the upgrade. If you need to downgrade the Connection Server instances, you must downgrade all Connection Server instances and then apply the backup to the last Connection Server that is downgraded.

When upgrading from a version of Horizon 7 earlier than Horizon 7 version 7.8, some user authentication settings will change. How these user authentication settings affect the user experience depends upon the client. See the Horizon Client documentation at https://docs.vmware.com/en/VMware-Horizon-Client/index.html. You must understand the usability and security implications of the user authentication settings before changing them. See, "Security-Related Server Settings for User Authentication" in the Horizon 7 Security document.