Chris_Nodak
Enthusiast
Enthusiast
‎11-28-2018 09:24 AM

Can you run different versions of connection server temporarily

I know that during an upgrade you should upgrade all connection servers at the same time. However we are in a situation where I am trying to move away from our existing security server model and implement a UAG.

I attempted to upgrade from 7.4 to 7.6 last week but had issues with the security server and had to roll everything back. I don't even want to mess with that server any longer.

I have deployed the UAG v3.3.1 and configured it for testing and am considering setting up a new connection server specifically for it with the thought that when we move to production with it, I can retire the old security server and the paired connection server. However I understand that UAG v3.3.1 isn't compatible with 7.4.

The question is, can I install an additional connection server with 7.6 and leave the existing connection server at 7.4 temporarily to ensure the UAG is functional, then cut over to it when it's ready for production? We also have an internal connection server running 7.4 as well.

Thanks.

Reply
BenFB
Virtuoso
Virtuoso
‎11-28-2018 11:26 AM

I would not recommend running mixed connection servers versions within a pod. It's only supported to run different versions in different pods with Cloud Pod Architecture (CPA) (e.g. Pod1 has two connection servers running 7.4.0 and Pod2 has two connection servers running 7.6.0).

For what it's worth I'm currently running UAG 3.3.1 using only Blast with Horizon 7.4.0 without issue. I would do the following.

  1. Add your additional connection server(s) running 7.4.0 and point the UAG to those (3.3.1 should work but if you need to be strict on compatibility deploy 3.3.0 and then once you upgrade to 7.6.0 upgrade the UAG).
  2. Decomission the security servers/connection servers.
  3. Upgrade the new connection server(s) from 7.4.0 to 7.6.0.

Horizon 7 Upgrade Overview

Important:

After you upgrade a Connection Server instance to the latest version, you cannot downgrade that instance to an earlier version. After you upgrade all Connection Server instances in a replicated group, you cannot add another instance that runs an earlier version.

Upgrade Connection Servers in a Replicated Group

Important:

If you do not upgrade all Connection Server instances in a replicated group, the health indicators in the Horizon Administrator dashboard might show that one or more instances are in an error state. This situation arises because different versions supply different kinds of data. The solution is to upgrade all instances in the replicated group.

View solution in original post

Reply
0 Kudos
Chris_Nodak
Enthusiast
Enthusiast
‎11-28-2018 12:41 PM

Yeah that's what I figured. I did deploy another 7.4 connection server and a 3.3.0 UAG. Now I'm just working on making the UAG work in our DMZ. Once I can successfully connect through it, we'll repoint the external production URL to it and I'll install our certificate.

Thanks for the info and good to know that 3.3.1 UAG is working for you with 7.4. I have a 3.3.1 ready to go, just will upgrade to it once I'm ready to move to 7.6.

Appreciate the response.

Reply
0 Kudos
BenFB
Virtuoso
Virtuoso
‎11-28-2018 12:43 PM

Good luck! That should work well for you. If you have any UAG questions feel free to make a new post. They can be a little tricky at first.

It's missing from the interoperability matrix but UAG 3.3.2 was released the beginning of October and might be worth looking at when you are ready. With the exception of critical updates VMware products typically see updates quarterly.

Release Notes for VMware Unified Access Gateway 3.3.2

Reply