This seems to be an oversight that the VMware team needs to correct. I would recommend filing an SR. Is there a specific reason you are looking at 2.9 or 3.0 as opposed to a newer version?
I'm upgrading an existing Horizon 7.1 environment to 7.6 including a pair of UAG's one being 2.9 and the other 3.0. I do not want to be in a position where the connections servers are upgraded first which then causes the UAG to stop working. UAG version 3.2.1 looks to be compatible with both 7.1 and 7.6 so I'm planning to deploy a new pair before the Horizon upgrade.
1 person found this helpful
3.2.1 is a stable release that I used with our Horizon 7.4.0 environment but you may leverage different pieces than I did. Just make sure to read the release notes as we've been burned by some issue in prior versions (RADIUS was broken in a two nic deployment with UAG 3.1, 3.2 and was fixed in 3.2.1). I just upgraded to UAG 3.3.1 in anticipation of moving to Horizon 7.6.0 and so far it's the best release to date.