The Microsoft Remote Desktop Connection Broker (RD Connection Broker) role has two responsibilities. First, since Windows Server 2012 the RD Connection Broker role always handles the initial RDP connection and sends the session to the RD Session Host with the least load. Second, the RD Connection Broker makes sure that users are able to reconnect to an existing (disconnected) session. Since Windows Server 2012, end users connecting to the environment always make an initial RDP connection to the RD Connection Broker. The RD Connection Broker then reroutes the user to the RD Session Host server with the least load (based on the load balancing mechanism within the RD Connection Broker) or reroutes the user to an existing (disconnected) session.

RDP traffic running on port 3389 must be load balanced in the LoadMaster.

After the RD Connection Broker role is installed, you can use the Remote Desktop Management Services (RDMS) console as part of the Server Manager to retrieve the RD Connection Broker servers as part of the deployment.