TS Session Broker Configuration

  • Article

Applies To: Windows Server 2008

In Windows Server 2008, Terminal Services Session Broker (TS Session Broker) supports a built-in load balancing functionality and supports configuring multiple IP addresses (including IPv6 addresses) to be used for redirection. Both of these capabilities are supported only by terminal servers running Windows Server 2008.

With TS Session Broker Load Balancing, when a user without an existing session connects to a terminal server in the load-balanced farm, the user will be redirected to the terminal server in the farm with the fewest sessions.

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

Events

Event ID Source Message

1010

Microsoft-Windows-TerminalServices-SessionBroker

 TS Session Broker had to switch the compression state in its directory to uncompressed.
Error code: %1.

1022

Microsoft-Windows-TerminalServices-SessionBroker

 Terminal Server %1 is not configured properly for redirection from legacy servers and should report only a single IP address to Session Broker.

1023

Microsoft-Windows-TerminalServices-SessionBroker

 TS Session Broker farm %1 is in an inconsistent state. For TS Session Broker load balancing to work correctly, all terminal servers in the same TS Session Broker farm must either be configured to use TS Session Broker load balancing or to not use TS Session Broker load balancing. Terminal servers that are running Microsoft Windows Server 2003 do not support TS Session Broker load balancing.

TS Session Broker

Terminal Services