On Mon, Mar 3, 2014 at 4:36 PM, Ken Cornetet <[email protected]> wrote: > 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).
Ok, so the fog thins a bit (I hope). Yes, I have just the one collection. So I should create a new A record - in my case, something like "rds-rdsh.domain.local", since I already made "rds.domain.local" an alias of my one and only web access host - and give it all 3 addresses of my session hosts. Then, when I publish my app, I go searching at "rds-rdsh.domain.local" to find it. This way, it's published with that round-robin DNS name, which is vital, rather than searching on any one particular session host. Yes? . > 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.
