Your web server will have its own unique A record (rdsweb.yourcompany.com).
You then create A records for each app server (rds.yourcompany.com). When you publish your apps, you use that name for the host. I can't remember if you need separate sets of A records for each collection (but with only three app servers, I assume you have one collection). What happens is this: Users log into the web site which shows the users the apps they have access to. When the user clicks, they get an RDS file that directs their client mstsc.exe to host "rds.mycompany.com". DNS gives mstsc.exe a list of corresponding IP addresses . mstsc.exe opens the first one in the list. If it fails, it tries subsequent ones. When mstsc.exe connects to an application server, that server queries the broker for the least loaded app server. The app server then sends a re-direct to mstsc.exe, which then connects to the target server. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Leone Sent: Monday, March 03, 2014 3:23 PM To: [email protected]; [email protected] Subject: [NTSysADM] Win 2012 RDS - load balancing advise 4 servers, all Win 2012 (not R2) I have 1 VM that is RDS Connection Broker, License Server, and Web Access. There are 3 VMs as session hosts. I am using published RemoteApps only, no full VDI. What I want to do is to enable load balancing. I have been advised, a couple months back: ----- The RDS application servers will load balance themselves (using the connection broker for load information). IIRC, it works thusly: You create a DNS A record for each app server using the same name (say,rds.yourcompany.com). You create a certificate with that name as the subject, and install it on each app server. You tell the web server to build the RDP files using that name as the host. When your clients pull the RPD files down from the web server, they launch the RDP client which resolves "rds.yourcompany.com" to a random* application server. When the RDP client attempts to connect to that server, that server asks the connection broker which is the least loaded app server in the farm. The app server then "redirects" the RDP client to the aforementioned least-loaded server. ----- So right now my CB has a domain wildcard certificate (*.domain.local).So based on the above, do I need to: - install that domain wildcard cert onto each Session Host - right now, I have "rds.domain.local" as an alias (C Name) of my CB/Web Access. I am unclear as to what changes I need to make to DNS. I don't want 4 records all saying "rds.domain.local", right, because the URL of the web server must be different from the session hosts. The end users will be entering "https://rds.domain.local"; as the URL they put into IE. I'm confused; can anyone shine a light? Thanks
