On Thu, Dec 12, 2013 at 3:57 PM, Ken Cornetet <[email protected]> wrote: > Your specs are probably a bit overkill for the app servers, and the web > server only needs two CPUs and 4GB.
The web server only has 2 vCPUs. (altho each with 2 cores) > You can easily run the web server, broker, and license roles on one server. OK, I can do that. I wasn't sure if that was a best practice or what. Our current Citrix environment has the licensing server separate from the web front ends (they use a hardware load balancer). > 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. We're not going to be having the clients launch the RDP client. Everything through web browser only. I'm not sure how that complicates things. (you mean "session host" when you say "app server", right?) > 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. > > * - DNS will use round-robin to hand these A records out UNLESS the client is > on the same IP subnet as one of the servers. Should not be, as the server subnet is different from the client subnet. I suppose it's possible that a developer might be on the same subnet and access it, but I doubt it. >In that case, the DNS server will always put that server in the top of the >list of returned addresses. But it doesn't matter -you aren't depending on >round-robin for load balancing anyway - unless you have RDP clients that are >too old to understand redirects. We do still have some XP clients, but they are being upgraded to Win 7. Thanks, that does help.
