Export (0) Print
Expand All
2 out of 3 rated this helpful - Rate this topic

Joining TS Session Broker

Updated: January 5, 2012

Applies To: Windows Server 2008

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.

Events

Event ID Source Message

1001

Microsoft-Windows-TerminalServices-SessionBroker-Client

The remote procedure call (RPC) to join TS Session Broker to %1 failed.
The following error occurred: Access Denied

1002

Microsoft-Windows-TerminalServices-SessionBroker-Client

The Terminal Services Session Broker service on server %1 is not available.

1005

Microsoft-Windows-TerminalServices-SessionBroker-Client

The server successfully joined a farm on the TS Session Broker server %1.

1006

Microsoft-Windows-TerminalServices-SessionBroker-Client

The server failed to join TS Session Broker. The RpcBindingReset function call failed with Win32 error code %1.

1007

Microsoft-Windows-TerminalServices-SessionBroker-Client

The server failed to join TS Session Broker. The RpcMgmtInqServerPrincName function call failed with Win32 error code %1.

1008

Microsoft-Windows-TerminalServices-SessionBroker-Client

The server failed to join TS Session Broker. The RpcBindingSetAuthInfoEx function call failed with Win32 error code %1

1009

Microsoft-Windows-TerminalServices-SessionBroker-Client

The server failed to join TS Session Broker. The RpcBindingSetOption function call failed with Win32 error code %1.

1010

Microsoft-Windows-TerminalServices-SessionBroker-Client

The server failed to join TS Session Broker. The RpcStringBindingCompose function call failed with error code %1.

1011

Microsoft-Windows-TerminalServices-SessionBroker-Client

The server failed to join TS Session Broker. The RpcBindingFromStringBinding function call failed with Win32 error code %1.

1012

Microsoft-Windows-TerminalServices-SessionBroker-Client

The server failed to join TS Session Broker.
Win32 error code: %1

1013

Microsoft-Windows-TerminalServices-SessionBroker-Client

The server failed to retrieve the local computer name.
Win32 error code: %1

1014

Microsoft-Windows-TerminalServices-SessionBroker-Client

The server failed to retrieve the security identifier (SID) of the TS Session Broker server.
Win32 error code: %1.

1015

Microsoft-Windows-TerminalServices-SessionBroker-Client

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.

Related Management Information

Terminal Server

Terminal Services

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.