Configuring Horizon Agent when multiple connection servers

[_mduchaine_]

Author : YeeChin

URL : http:////docs.vmware.com/en/VMware-Horizon-7/7.0/com.vmware.horizon-view.desktops.doc/GUID-06794FA2-...

Topic Name : Install Horizon Agent on a Remote Desktop Services Host

Publication Name : Setting Up Desktop and Application Pools in View

Product/Version : VMware Horizon 7/7.0

Question :

Hello, In case you have multiple connection servers behind a load-balancer, which connection server do you specify when configuring the agent?

[jlenag]

For the intital setup, it doesn't matter what connection server you point it to.  This is just to register the RDS host to Horizon and to a farm.  Once the entire setup is complete, all your connection servers will use the farm from Horizon and everything should work just fine.

[_mduchaine_]

Hi jlenag,

Thanks for your reply.

From the network port diagrams, it looked as if only the first cnx server was used and replica cnx servers got it via JMS through the first cnx servers.

Good to hear agent registration is not limited to the first one. I was worried about redundancy:

I get the information is replicated across all connection servers and any will be able to use the RDS host.

Yet the agent is still pointing to a single connection server, regularly exchanging messages on ports 4001, 4002.

So what happens when that cnx server goes down for a decent amount of time: the agent goes offline and so does the RDS resources, right?

Shouldn't there be a better way than to point to just a single cnx server when you have multiple?

[jlenag]

From my understanding, the only thing that would break if a connection server went down was any sessions being brokered by it.  I would highly doubt that a RDS Farm would go down if only one connection server was down.  I would think it would simply talk to the other ones in the cluster.

This would be an easy enough thing to test, but I'm betting the farm won't even notice if one of the servers is down for a period of time.

[cbaptiste]

The farm would not care if a connection server is down unless you use restrictions and tied application to a specific connection server. The most that would happen is your users losing connections. Next time a user attempts to reconnect, the load balancer will detect the broker is failing monitoring and will send the traffic to an active broker which if in the same Pod will have the user's existing session and reconnect the user to it.