WIN2008 Configure Terminal Services Network Load Balancing combat

Terminal Services Session broker (TS session Broker) is included in Windows Server (R) 2008 Standard, Windows Server 2008 Enterprise, and Windows Server 2008 Datace Nter, it can track disconnected sessions on a Terminal server farm and ensure that users are reconnected to these sessions. In addition, the use of TS session Broker can also load-balance sessions between terminal servers in the farm. This feature is provided by the TS session Broker load Balancing feature. However, this session-based load Balancing feature requires a front-end load balancing mechanism to distribute initial connection requests to a Terminal server farm. You can distribute initial connection requests using load balancing mechanisms such as DNS loops, NLB, or hardware load balancers. By simultaneously deploying NLB and TS session Broker load Balancing, you can take advantage of the functionality that NLB provides for network-based load balancing and problem server detection, TS session Broker load balancing based on session load balancing, and a limit on the number of pending logon requests per server.

Terminal Services Components

Terminal Services contains the following two components that are important to build load balancing: Terminal Services session Broker service and Terminal Services Configuration snap-in.

Terminal Services session Broker Service

The service maintains a database that tracks Terminal Server sessions in a load-balanced Terminal server farm and provides terminal server with information to connect users to existing sessions.

When you start the Terminal Services session Broker service, it creates the sessions Directory Computers local group. By default, the group is not populated. You must select each Terminal Server or group to join the Terminal Services session Broker service, and then manually change its group membership to the sessions Directory Computers group.

The Terminal Services Session Broker service starts automatically when you install the TS Session Broker role service on a server that you want to use to track user session information in a load-balanced Terminal Server farm. You can use a TS session Broker server to track user sessions in multiple server farms because the performance overhead is minimal.

When you install the TS session Broker role service, the following changes are made on the local computer:

Installs the Terminal Services session Broker service. By default, the service is set to started and automatic.

Create a session Directory Computers local group.

Prerequisites for Installation

The server on which the TS session Broker role service is installed must be a domain member.

Windows Server 2008-based servers that install the TS session Broker role service do not have to be terminal servers or enable Remote Desktop.

installation process

If you do not have any Terminal Services role services installed, use the following procedure to install the TS session Broker role service.

To install the TS session Broker role service:

1, click Start, point to Administrative Tools, and then click Server Manager.

2, under Role Summary, click Add Role.

3. In the Add Role Wizard, check the before you start page, and then click Next.

4, on the Select Server Role page, select the Terminal Services check box, and then click Next.

5, on the Terminal Services page, click Next.

6. On the Select Role Service page, select the TS session Broker check box, and then click Next.

7. On the Confirm Installation Selection page, confirm that TS session Broker is listed, and then click Install.

8, on the Installation Results page, click Close.