Event ID 1015 — Joining TS Session Broker

Updated: January 5, 2012

Applies To: Windows Server 2008

yellow

Terminal Services Session Broker (TS Session Broker) is a Terminal Services role service in Windows Server 2008 that supports session load balancing between terminal servers in a farm, and reconnection to an existing session in a load-balanced terminal server farm.

In order for the terminal server to join a farm in TS Session Broker, the terminal server must be able to communicate with the TS Session Broker server across the network. In addition, the computer account for the terminal server must be a member of the Session Directory Computers local group on the TS Session Broker server.

Note:  TS Session Broker was formerly called Terminal Services Session Directory.

Event Details

Product: Windows Operating System
ID: 1015
Source: Microsoft-Windows-TerminalServices-SessionBroker-Client
Version: 6.0
Symbolic Name: EVENT_NO_LB2003
Message: This terminal server cannot participate in TS Session Broker load balancing because the server is configured to use a Microsoft Windows Server 2003-based Session Directory server %1. The Session Directory feature in Windows Server 2003 does not support Terminal Services Session Broker load balancing.

Resolve

Use a Windows Server 2008-based TS Session Broker server

To resolve this issue, configure the terminal server to use a Windows Server 2008-based TS Session Broker server.

A Windows Server 2008 terminal server that is configured to use the TS Session Broker Load Balancing feature cannot be configured to use a Windows Server 2003-based Session Directory server, because a Windows Server 2003-based Session Directory server does not support the TS Session Broker Load Balancing feature.

If you have an existing Windows Server 2008-based TS Session Broker server in your environment, you can configure the terminal server to use that server. Otherwise, you should consider upgrading the existing Windows Server 2003-based Session Directory server to Windows Server 2008 or not using the TS Session Broker Load Balancing feature.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To configure the terminal server to use a Windows Server 2008-based TS Session Broker server:

  1. On the terminal server, open Terminal Services Configuration. To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Under TS Session Broker, double-click Member of farm in TS Session Broker.
  4. On the TS Session Broker tab, under TS Session Broker server name or IP address, enter the computer name or IP address of a Windows Server 2008-based TS Session Broker server.
  5. Click OK to close the Properties dialog box.

Verify

To verify that the terminal server has successfully joined a farm in TS Session Broker, use either of the following methods:

Method one

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

  1. On the terminal server, open Event Viewer. To open Event Viewer, click Start, point to Administrative Tools, and then click Event Viewer.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the left pane, expand Windows Logs, and then click System.
  4. Look for an event with a Source of TerminalServices-SessionBroker-Client and an Event ID of 1005. This event indicates that the terminal server has successfully joined a farm in TS Session Broker.

Method two

  1. On the terminal server that has been joined to a farm in TS Session Broker, start a new Terminal Services session.
  2. After the session is established, disconnect the session.
  3. On a different terminal server, but one that is also a member of the same farm in TS Session Broker, try to reconnect to your existing session. If you are able to reconnect to the existing session, the terminal server is successfully joined to a farm in TS Session Broker.

Related Management Information

Joining TS Session Broker

Terminal Services

Community Additions

ADD
Show: