!!HOT!! Download Vmware Horizon Connection Server
Gunvor Nazarian
Need to migrate the standard connection server from a 2012 server MS OS to 2019 MS OS. Can I create a replica of the 2012 connection server or does the new 2019 need to be a standard deployment? We have another connection server that used the 2012 standard to replicate from as well. If I have to use standard for the 2019 OS buildout does that also mean i need to replicate the other connection server off the new 2019 standard?
We are currently using the built-in HA features for UAGS and a primary connection server and a replica connection server. No load balancer. Had the primary connection server go down and connections failed to the replica. Started digging into DNS and found we never add an entry for examplevdi.domain.com for the replica server.
So if a primary connection server goes down and there is no load balancer then manual intervention should happen by changing the DNS record to point to the replica? Or is there a better way to go about it?
I have had this problem since the beginning, about a year ago. I'm on Horizon 7.13. This system was installed and setup by a consultant, first mistake. He was was given an impossible time line, second mistake. The problem is this. Almost all users are being directed to one Connection Server, I have two. It will not balance out the session between the two servers. I use a pair of UAG servers. Their connections are fairly balanced between them. They communicate with a load balancer in front of the Connection Servers. The load balancer has been checked twice and it's configuration verified by the vendor. I have talked to vmware support more than once and currently have an open case. Does anyone have any ideas why all sessions seem to gather on one Connection Server?