VMware Unified Access Gateway – Upgrade to v. 3.9

Release date: March 19th 2020

Welcome to my VMware Unified Access Gateway series. The new version of Unified Access Gateway, 3.9, was GA on March 17th 2020. In this section I will describe how I upgraded my UAG’s to v. 3.9

To check out all the new features and changes with VMware Unified Access Gateway  3.9, read the release notes from VMware posted here: Release Notes for VMware Unified Access Gateway 3.9

UAG-Upgrade_3.6-3.9-01

 

Prior to upgrading my existing UAG’s, I have upgraded my Horizon environment to v. 7.12. When I check VMware Product Interoperability Matrices, I see that UAG 3.9 is only compatible with Horizon 7.12, which is OK for me as I only use UAG for Horizon pr. now.

UAG-Upgrade_3.6-3.9-02

 

First, I download the necessary media from MyVmware.com to my deployment server. Next I export the settings before I start upgrading.

UAG-Upgrade_3.6-3.9-03

 

I copy the new ova and uagdeploy powershell files to my working directory

UAG-Upgrade_3.6-3.9-04

 

Then I edit ini-files with new ova filename

UAG-Upgrade_3.6-3.9-05

 

I redeploy UAG with the new ova-file using the existing ini-files. As we can see from the screenshot below, the script automatically shuts down the existing UAG and deletes it, before deploying the new UAG using the settings I defined in the ini-files.

UAG-Upgrade_3.6-3.9-06

 

When the new UAG is deployed and ready, I log in and have to change password, before I get access to the management UI.

UAG-Upgrade_3.6-3.9-07

UAG-Upgrade_3.6-3.9-08

UAG-Upgrade_3.6-3.9-09

 

I verify Horizon Settings inside UAG

UAG-Upgrade_3.6-3.9-10

 

When I login to VMware Horizon Administrator, I can see that the Gateways are unreachable

UAG-Upgrade_3.6-3.9-11

UAG-Upgrade_3.6-3.9-12

 

The reason for the error above, is that the powershell script doesn’t adjust the UAG Name with the name I put in the ini-file. (I have absolutely no idea why). I manually adjust this in the UAG System Configuration

UAG-Upgrade_3.6-3.9-13

UAG-Upgrade_3.6-3.9-14

 

After I change the UAG Name, the Connection Server correctly reaches my UAG’s and the errors disappears

UAG-Upgrade_3.6-3.9-15

UAG-Upgrade_3.6-3.9-16

 

Finally, I do a test by logging in to Horizon through the UAG to verify functionality.

 

VMware Unified Access Gateway – Upgrades

VMware Unified Access Gateway planning, deployment etc.

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.