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. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Leone Sent: Tuesday, March 04, 2014 10:28 AM To: [email protected] Subject: Re: [NTSysADM] Win 2012 RDS - load balancing advise On Tue, Mar 4, 2014 at 10:20 AM, Michael Leone <[email protected]> wrote: > On Tue, Mar 4, 2014 at 9:54 AM, Michael Leone <[email protected]> wrote: >>> You then create A records for each app server (rds.yourcompany.com). When >>> you publish your apps, you use that name for the host. > >> 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? > > No. Or, at least, that's not what's happening for me. When I try to > publish an app, and browse to "\\rds-rdsh.domain.local\d$\folder" > (using the new DNS name I just created, and not the name of any > specific session host), it tells me that I can't do that, and that I > need to go to a specifically named session host path. I wonder if that is due to the fact that this is an old app, and the vendor tells me to just copy the installed folder structure from my current Citrix environment. i.e., not to run an actual install or setup routine, just copy the folder over. Thus, when I go to publish an app, this app is *not* in the list of installed apps that seems to get pulled from the session host, so I need to go browse to the folder where it is installed on one of the session hosts and add it that way.
