Configure TS Session Broker Settings by Using Group Policy
Applies To: Windows Server 2008
You can use Group Policy to configure TS Session Broker settings. However, to configure the IP addresses to be used for reconnection, or to configure the relative server weight when using TS Session Broker Load Balancing, you must use Terminal Services Configuration.
To assign TS Session Broker settings through Group Policy, it is a best practice to group the terminal servers that are in the same terminal server farm into a single organizational unit (OU) in Active Directory Domain Services (AD DS). Then, configure the TS Session Broker settings in a Group Policy object (GPO) that applies to the OU.
For the TS Session Broker settings to be effective on a server, the server must have the Terminal Server role service installed.
The following procedure describes how to configure TS Session Broker Group Policy settings by using the Group Policy Management Console (GPMC).
To change Group Policy settings for a domain or an OU, you must be logged on as a member of the Domain Admins group, Enterprise Admins group, or the Group Policy Creator Owners group, or have been delegated the appropriate authority over Group Policy to complete this procedure.
To apply TS Session Broker settings to an Active Directory OU
To start the GPMC, click Start, point to Administrative Tools, and then click Group Policy Management.
In the left pane, locate the OU that contains the terminal servers.
To modify an existing GPO for the OU, expand the OU, and then click the GPO.
To create a new GPO, follow these steps:
Right-click the OU, and then click Create a GPO in this domain, and link it here.
In the Name box, type a name for the GPO, and then click OK.
In the left pane, locate and then click the new GPO.
In the right pane, click the Settings tab.
Right-click Computer Configuration, and then click Edit.
In the left pane, under Computer Configuration, expand Policies, Administrative Templates, Windows Components, Terminal Services, Terminal Server, and then click TS Session Broker.
In the right pane, double-click the Join TS Session Broker policy setting, click Enabled, and then click OK.
Double-click the Configure TS Session Broker farm name policy setting, and then do the following:
In the TS Session Broker farm name box, type the name of the farm in TS Session Broker that you want to join, and then click OK.
TS Session Broker uses a farm name to determine which servers are in the same terminal server farm. You must use the same farm name for all servers that are in the same load-balanced terminal server farm. Although the farm name in TS Session Broker does not have to be registered in AD DS, it is recommended that you use the same name that you will use in DNS for the terminal server farm. (The terminal server farm name in DNS represents the virtual name that clients will use to connect to the terminal server farm.) If you type a new farm name, a new farm is created in TS Session Broker and the server is joined to the farm. If you type an existing farm name, the server joins the existing farm in TS Session Broker.
Double-click the Configure TS Session Broker server name policy setting, and then do the following:
In the TS Session Broker server name box, type the name of the server where you installed the TS Session Broker role service, and then click OK.
To use TS Session Broker Load Balancing, double-click the Use TS Session Broker load balancing policy setting, click Enabled, and then click OK.
Optionally, if you have a hardware load balancer that supports TS Session Broker token redirection, double-click Use IP Address Redirection and configure the setting. For more information, see the Group Policy Explain text and Configuring Dedicated Redirectors (optional).
To configure TS Session Broker settings by using local Group Policy, use the Local Group Policy Editor. To start the Local Group Policy Editor, click Start, click Run, type gpedit.msc, and then click OK. To configure local Group Policy settings, you must be a member of the Administrators group on the local computer or you must have been delegated the appropriate authority.