asked on

Do I need Remote Desktop Connection Broker

I am deploying Remote Desktop Session Hosts at my remote offices, one per location. Do I need to have the RD Connection Broker role installed? This isn't a farm in the classic sense. If I do need the connection broker role, would it just go on the session host? I am familiar with how it works for Windows 2008 R2, but things seemed to have changed with Windows 2012 R2. For example, the documentation that I have seen says to configure the license server at the Connection Broker. In the old days we didn't even need the connection broker!

I have a separate license server that I will use for all of my servers. I will also be setting up separate NLB clusters for the RDWA and RDGW roles.

ASKER CERTIFIED SOLUTION

Cliff Galiher

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Brad Bouchard

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

kevinhsieh

ASKER

I am adding the connection broker service. I will let you know if I have any issues with the configuration.

kevinhsieh

ASKER

I've requested that this question be closed as follows:

Accepted answer: 300 points for cgaliher's comment #a39996861
Assisted answer: 200 points for xBouchardx's comment #a40000304
Assisted answer: 0 points for kevinhsieh's comment #a40000702

for the following reason:

The deployment model and management is a bit different from 2008 R2. It looks like most management is done from the connection broker, that that seems to be a required role now.

Brad Bouchard

So then we both answered your question so I object and suggest that points be split evenly between myself and Cliff.