The Server 2008 R2 RDS broker only looked at the number of users on an app server to derive a load metric. I don't know if 2012 added any additional criteria or not.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Leone Sent: Tuesday, March 04, 2014 11:42 AM To: [email protected] Subject: Re: [NTSysADM] Win 2012 RDS - load balancing advise On Tue, Mar 4, 2014 at 11:06 AM, Ken Cornetet <[email protected]> wrote: > I don't have an RDS environment to look at right now, and I've played with > RDS on server 2008 R2 and 2012, so I might be getting the two conflated. > > I recall that you have to somehow create RDS files, and then make them > available to the web server to publish. I can't recall the details. I do > remember that server 2012 hides a lot of this detail - the wizard does most > of the work for you. > > The DNS round-robin isn't critical to load balancing. You could create RDS > files pointing to a single app server. The broker would still load balance by > telling that server to redirect clients to a less loaded server. The reason > you use multiple A records is so that if one app server is down, mstsc.exe > will try another for the initial connection. And you are correct! I published my app, by pointing to folder on one app server (i.e., the program I wanted was not in the list of installed programs of the app server), and then had 3 users all access that RemoteApp. And the Connections box on the Broker shows all 3 on different app servers. So it looks like it *is* doing it's own load balancing (well, more round robin executing than actually balancing the load, I think), without any special help from me. Kewl!
