If your deployment uses load balancers to manage multiple Horizon Connection Server instances, an upgrade of the Horizon Connection Server infrastructure can be performed with zero down time.
After you have performed a fresh install or upgraded all Horizon Connection Server instances to the new version of Omnissa Horizon 8, you cannot downgrade the Horizon 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 Horizon Connection Server instances while planning an upgrade to the new version of Horizon 8, you must back up the Horizon Connection Server instances before starting the upgrade. If you need to downgrade the Horizon Connection Server instances, you must downgrade all Horizon Connection Server instances and then apply the backup to the last Horizon Connection Server that is downgraded.
When upgrading from a version 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 Omnissa Horizon Client documentation. You must understand the usability and security implications of the user authentication settings before changing them. See Security-Related Server Settings for User Authentication.
If you have a perpetual or term license, after upgrading a Horizon Connection Server in a pod to the new version of Horizon 8, you cannot start a desktop from this Horizon Connection Server but you can start a desktop from other Horizon Connection Servers in the pod. To start a desktop from the upgraded Horizon Connection Server, start Omnissa Horizon Console on this Horizon Connection Server and enter a license key for the new version. Then you can start desktops from all Horizon Connection Servers in the pod.
After upgrading a Horizon Connection Server instance, perform a hard reload of the Horizon Console browser, so that it picks the latest HTML5 UI source code from the Horizon Connection Server.
Note: You can also use Horizon Lifecycle Management (LCM) APIs to automate upgrades of Horizon Connection Server. For more information, see Automating Installations and Upgrades of Omnissa Horizon 8 With LCM APIs.
After upgrading to Horizon version 2503 from a previous version, we recommend that you plan and perform updating the partition names to the new ones. For details, refer to KB article 6000797.
Was this page helpful?