RDS 2012 - configuration/deployment questions


I am in the process of building an RDS deployment with Session Broker and Session Host servers (no Gateways). That being said I would like to deploy the following servers:

1. RDSCB01 (Connection Broker)
2. RDSCB02 (Connection Broker)
3. RDSHost01 (Host)
4. RDSHost02 (Host)

I would like to configure the brokers in HA - I don't have external Load Balancers just native Microsoft can be used for this project.

Connection Broker: There are multiple articles on how to setup 2 Broker servers in HA. Example: http://thewolfblog.com/2014/02/02/configuring-ha-for-the-remote-desktop-connection-broker/ 

A few questions:

If I configure DNS RR for the brokers if one the servers is down then there is a potential that users will continue to go the server that's not available - correct?

-To avoid that can I get the Broker servers configured through MS native NLB? The Broker servers are going to be VMs running from Hyper-V nodes. If so, can someone provide a "How to guide" that explains the process.

Session Host Collections - Multiple Servers

I would like to create a collection that will include RDSHost1 and RDSHost2, as far as I know natively you can configure both servers to be Load Balanced through the deployment Wizard (In Overview, right-click RD Session Host and click Add RD Session Host Servers.)

How is that going to work if one of the Host Servers that belong to that collection is down? Are new connections going to be sent to any of the available servers?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
First, I *strongly* recommend adding one or more RDWA servers to your current plan. Because of the re-architecture of RDS in 2012, manually setting up the RDP clients with settings just doesn't work the way you expect.  For example, there is no GUI to specify the RDCB, and while you can connect to a session host directly, if you skip the RDCB, you lose all of the load balancing and session affinity it provides.  RDWA is the mechanism by way you get accurate and full .rdp files without manual editing and without having to provide complicated instructions to users.   There is a reason the RDWA role is created during a default "quick" deployment. It is considered core to the infrastructure at this point.

So, with that in mind, here are the answers to your questions:

As for your second question, the connection broker handles managing connections, so in the case of an outage of one server, the connection broker will be aware and will redirect traffic to the remaining servers in the collection. So as long as your RDCB deployment is healthy, this will also "just work."

If you properly configure DNS RR for the connection broker, even if one is down, the modern RDP clients from Microsoft accommodate this. You neither need an external load balancer or NLB. The intelligence is baked into the client.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
llaravaAuthor Commented:
1.) I just want to provide full session desktop access to my users no need to provide Remote App, that being said do I need to deploy WebAccess at all or simply by providing the DNS record for connection broker DIP (NLB) should be sufficient for them to access the environment?

2.) One more thing with RDSH collections - If a server is down how does the system know does the client know that is down to not send the traffic to it? Do you need an external Load Balancer? Does it work with RR (if so do you need a single DNS name for the collection?) if it's natively how is that error detection logic works?

3.) Also using RR DNS will present the user with an issue if one of the broker servers are down and they are send to it? Is there anything built in the RDP client to prevent this from happening of this is just Regular RR DNS with it's downside?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.