Skip to content
vJAL.nl
  • Partners
    • BDRSuite by Vembu
  • About me
  • Home
  • Search Icon
Parallel upgrading of Horizon Connection Servers (Horizon 8 2006+)

Parallel upgrading of Horizon Connection Servers (Horizon 8 2006+)

11 January 2021 Jesper Alberts Comments 0 Comment

Since the release of Horizon version 2006 it’s possible to upgrade your Connection Servers in parallel. Instead of upgrading them one by one, you can now upgrade all Connection Servers (up to a maximum of three pods) simultaneously. Which can save you a huge amount of (down)time!

In this blog post I’ll quickly share my experience and show you how the process works.

Table of Contents

  • Prerequisites
  • Upgrading the first Connection Server
  • Upgrading the remaining Connection Servers in parallel
  • Conclusion

Prerequisites

  • Verify there are no issues with Horizon LDAP replication
    • To check the replication status of the local LDAP instance, run the following command:
      repadmin.exe /showrepl localhost:389
    • To check the replication status of the global LDAP instance in a Cloud Pod Architecture, run:
      repadmin.exe /showrepl localhost:22389
  • Upgrade one Connection Server manually to determine there are no issues with Horizon LDAP replication. After you resolve any errors during the upgrade process, you can proceed to upgrade multiple Connection Servers in parallel.
  • Bring up all the LDAP nodes in the Connection Server cluster before the upgrade. This ensures that the schema master node is available on the cluster.
  • All other prerequisites for upgrading a Connection Server still apply, as described here.

Upgrading the first Connection Server

Before upgrading the first Connection Server I made sure it was disabled from the Horizon Console and my load balancer.
The upgrade of a Connection Server itself is fairly straight forward, as you can tell from the screenshots below

(click to enlarge)

After this we have upgraded a single Connection Server to version 2012 (8.1) as shown on the screenshot above.

Upgrading the remaining Connection Servers in parallel

Before starting the parallel upgrades, I verified if LDAP replication was still successful. As this was the case I could now disable the remaining Connection Servers and start the upgrade(s).

The upgrade process of the remaining Connection Servers remains the same, the only difference is we can now run them simultaneously.

(click to enlarge)

Conclusion

I wanted to test the parallel upgrading ever since I saw this mentioned in the release notes of version 2006. It’s a great way to save time, especially when running a large(r) amount of Connection Servers across multiple pods. 

After upgrading the first Connection Server it took me approximately 15 minutes to upgrade the remaining Connection Servers. With this feature I can see the duration of maintenance windows being reduced drastically.

I would however love to see the upgrade process moved to a central location, as you see with other VMware products, to make the process even easier.

Please follow and like us:
Tweet

Horizon
Horizon, ITQ, Upgrading

Post navigation

PREVIOUS
Testing the “True SSO configuration utility” fling
NEXT
Quick tip: Controlling SEGv2 cipher suites and scoring an A+ at SSL Labs

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Let’s stay in touch!

Twitter
LinkedIn

Blog sponsors

Recent Posts

  • Introducing BDRSuite v5.5.0 [sponsored]
  • Vembu Backup for Endpoints [sponsored]
  • Renewing your NVIDIA licenses on the DLS appliance
Twitter feed is not available at the moment.

Archives

  • December 2022
  • October 2022
  • August 2022
  • July 2022
  • June 2022
  • March 2022
  • August 2021
  • January 2021
  • October 2020
  • August 2020

Categories

  • BCDR
  • Certification
  • Dynamic Environment Manager
  • Horizon
  • NVIDIA vGPU
  • Partners
  • Personal
  • PowerCLI
  • Secure Email Gateway
  • UAG
  • Uncategorized

Tags

Back-up BCDR Certificates Certification DEM Dynamic Environment Manager Horizon Identity Manager ITQ Job Licensing Microsoft 365 NVIDIA Personal PowerCLI Replication SEG SEGv2 SSL SSLLABS Troubleshooting True SSO UAG Upgrading VCAP VCIX Vembu vGPU VMware Tools VMware vSphere Workspace One Access
© 2023   All Rights Reserved.
Manage Cookie Consent
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage vendors Read more about these purposes
View preferences
{title} {title} {title}