VMware Horizon – Upgrade Horizon Connection Servers to v. 2203

Release date: May 9th 2022

Welcome to my VMware Horizon series. In this session I will describe how I upgraded my VMware Horizon Connection Servers to v. 2203. Although this isn’t strictly necessary according to the Release Notes, I will go through the motions in order to have every component in my Horizon infrastructure on the same version. I start out by downloading the installation media from VMware Customer Connect

Prior to doing my Cloud Pod Architecture upgrade, I double check VMware’s documentation about upgrading CPA here: Upgrading a Cloud Pod Architecture Environment

As always when upgrading VMware Horizon, before I start upgrading my Connection server, I verify that I have a valid backup and document my settings. I also disable the provisioning and desktop pools

UpgradeConnectionServer-01

Next, in Horizon Administrator, I disable the connection server I want to upgrade.

UpgradeConnectionServer-02

As I’m running Cloud Pod Architecture, I also check that replication between my connection servers are running smoothly, as described by VMware here: Forcing replication between ADAM databases This also applies to replica servers and became a problem when I was upgrading to 2111, documented here: VMware Horizon – Upgrade Horizon Connection Servers to v. 2111 Anyway, once I had sorted out the issue above, I could start the upgrade by first verifying the installed versions from Control Panel

Next, I login on the first Connection Server and perform a silent upgrade on my Connection Server below, running the command below, as described in VMware’s documentation: Silent Installation Properties for a Horizon Connection Server Standard Installation

VMware-Horizon-Connection-Server-x86_64-8.4.0-19446835.exe.exe /s /v"/qn VDM_SERVER_INSTANCE_TYPE=1 VDM_INITIAL_ADMIN_SID=S-1-5-32-544"

Once the upgrade is finished I can verify in Event Viewer that the upgrade was successful

I can also see that the correct version is installed in Control Panel

Next, I do a reboot of the Connection Server. Once it is up again, I check that the Horizon Services has started properly

As the upgrade of Connection Servers normally resets my Clients Repository, I have to set up this again. This I have documented here: VMware Horizon – Upgrade Client repository with Horizon 2203 Clients

Finally I log in on the VMware Horizon Administrator Console and enable the Connection Server and the desktop pools that I disabled to begin with. I also check that all my settings etc. has been preserved through this upgrade.

UpgradeConnectionServer-10

As a result of the upgrade, I check if I have to recreate my locked.properties file under:

C:Program FilesVMwareVMware ViewServersslgatewayconf

This concludes my session about upgrading the Connection Servers to v. 2203. I can now proceed with upgrading the UAG’s, posted here: VMware Horizon – Upgrade Unified Access Gateway to v. 2203

VMware Horizon – Upgrades

VMware Horizon planning, deployment etc.

Official VMware Horizon 8 Documentation

Disclaimer: Every tips/tricks/posting I have published here, is tried and tested in different it-solutions. It is not guaranteed to work everywhere, but is meant as a tip for other users out there. Remember, Google is your friend and don’t be afraid to steal with pride! Feel free to comment below as needed.

%d bloggers like this: