VMware Horizon Community
Jbir
Enthusiast
Enthusiast

URL Configuration for multiple connection servers

Hi,

I have looked at a few posts about this but none seem to cover exactly what i am struggling with. We have Horizon Enterprise 6.0.1 installed.

I have setup a connection server (viewa) and a replicated connection server (viewb).

I wanted the clients to connect to a standard url vdi.company.com. We have a wildcard certificate *.company.com so I installed the wildcard cert on viewa, edited the friendly name to be vdm (removed vdm from the view created server cert) rebooted and added vdi.company.com to the DNS and all is well.

I have also installed the wildcard certificate on viewb and made the friendly name vdm – all well.

However, if I am using a load balancer (only tested playing with DNS round robin, but possibly will use F5 in the future) currently, how do I configure the URLs for the connection servers in View Administrator?

Currently I am only using viewa so I have the urls set as vdi.apps.nerc.ac.uk:443 and vdi.apps.nerc.ac.uk:8443, however if I want to bring viewb into the equation with a round robin I cannot have it’s urls also set to vdi.company.com. If I leave the urls pointing to the server names (viewa.company.com:8443 etc) when the html access redirects to the connection server when you select a desktop to log onto it is then untrusted.

Any advise out there on how this should be configured? We won't be using a security server. External connections will go through a Juniper portal and internal off-site through a TMG gateway (soon to be F5).

Reply
0 Kudos
2 Replies
kgsivan
VMware Employee
VMware Employee

Define and register a new name with Load balance IP address. Let us say view-ab.company.com.

When DNS resolve this address it should resolve the external IP of the load balancer.

Now, login to view administrator console either viewa or viewb

go to view configuration, servers, select connection servers tab, both viewa and viewb will be listed out there.

select viewa, and click edit, select http(s) secure tunnel, and at the external URL filed give https://view-ab.company.com:443/

sample.png

Save the settings.

Now repeat same steps for all remaining connection server, and give same external URL

Now when users connection via https://view-ab.company.com:443/ it will be load balanced across all connection servers.

(in certificates you can use subject alternative name)

Reply
0 Kudos
Jbir
Enthusiast
Enthusiast

Thanks for that. We are just setting it up through TMG at the mo. Not sure what that is like for load balancing, is probably a bit more like DNS round robin, but that would do the job for us for now. We are moving to F5 soon.



Reply
0 Kudos