Remote Desktop Services Configuration When the Session or Connection Broker Is Deployed

This article describes how to configure Remote Desktop Services to work with the Barracuda Load Balancer ADC.

Step 1: Configure the Session or Connection Broker with Remote Desktop Services

The Session Broker provides a mechanism for a disconnected user to be reconnected to the server that has its disconnected session. Installing the Session Broker greatly improves the overall experience for end-users; installation is optional but highly recommended by Barracuda Networks.

This article describes how to install and configure the Session Broker with Remote Desktop Services in Windows; if you choose not to deploy the Session Broker, ensure the following:

Verify the Group Policy for the domain does not allow for disconnected sessions.
Verify users are limited to one connection in a Group Policy Object for your domain.

For Windows Server 2008 R1 or R2, complete the installation and configuration described below on the Session Broker server to ensure that its settings are correctly configured.

Install the Session Broker role service on a server by completing the following steps:

Set up a Session Brokerage privileges list to tell the Session Broker which computers are authorized to be brokered; complete the procedures that correspond with your environment.

If the Session Broker is located on a server that is also a domain controller, complete the following steps:

If the Session Broker is not on a server that is also a domain controller, complete the following steps:

For more information about Remote Desktop Services in Windows Server 2012 or 2012 R2, refer to the Windows 2012 RDS Deployment Overview in the Load Balancing Microsoft Remote Desktop Services Deployment Guide.

Step 2: Configure the Remote Desktop Session Host Server

For Remote Desktop Services in Windows Server 2008 R1 or R2, complete the following steps on all Remote Desktop Session Host servers:

For Remote Desktop Services in Windows Server 2012 or 2012 R2, use either a Group Policy Object that applies to all Remote Desktop Session Host servers or configure each server individually using local group policy:

When you have completed these procedures, return to Remote Desktop Services Deployment (Including Remote Desktop Gateway).