Export (0) Print
Expand All

RD Connection Broker Communication

Published: January 8, 2010

Applies To: Windows Server 2008 R2

Remote Desktop Connection Broker (RD Connection Broker), formerly Terminal Services Session Broker, is a Remote Desktop Services role service in Windows Server 2008 R2 that supports session load balancing between RD Session Host servers in a farm, connections to virtual desktops, and reconnection to an existing session in a load-balanced RD Session Host server farm. For RD Connection Broker to work properly, the RD Session Host server must be able to communicate with the RD Connection Broker server across the network.

Events

Event ID Source Message

1013

Microsoft-Windows-TerminalServices-SessionBroker-Client

The server failed to retrieve the local computer netbios name.
HRESULT = %1

1014

Microsoft-Windows-TerminalServices-SessionBroker-Client

The server failed to retrieve the local computer FQDN.
HRESULT = %1

1015

Microsoft-Windows-TerminalServices-SessionBroker-Client

This Remote Desktop Session Host server cannot participate in RD Connection 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 Remote Desktop Connection Broker load balancing.

1280

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Services failed to join the Connection Broker on server %1.
HRESULT = %2

1281

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Services successfully joined a farm on the Connection Broker server %1.

1282

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Services failed while leaving the Connection Broker on server %1.
HRESULT = %2

1283

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Services successfully left a farm on the Connection Broker server %1.

1284

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Connection Broker Client failed to initialize while joining the Connection Broker on server %1.
HRESULT = %2

1296

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User : %1\%2
HRESULT = %3

1297

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Connection Broker Client successfully received redirection packet from Connection Broker.
User : %1\%2

1298

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Connection Broker on server %1 failed to repopulate sessions.
HRESULT = %2

1299

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Connection Broker on server %1 returned error on %2 notification.
Session Id : %3
HRESULT = %4

1300

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Connection Broker Client rejected a call from an unauthorized ip address %1.
HRESULT = %2

1301

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Connection Broker Client received request for redirection.
User : %1\%2
RDP Client Version : %3

1302

Microsoft-Windows-TerminalServices-SessionBroker-Client

%2 existing sessions were successfully repopulated on Remote Desktop Connection Broker server (%1).

1303

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Connection Broker on server %1 failed to get Cluster credentials.
HRESULT = %2

1304

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Connection Broker client successfully retrieved Cluster credentials from Connection broker (%1).

1306

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Connection Broker Client failed to redirect the user %1\%2.
HRESULT = %3

1307

Microsoft-Windows-TerminalServices-SessionBroker-Client

Remote Desktop Connection Broker Client successfully redirected the user %1\%2 to the endpoint %3.
Ip Address of the end point = %4

1308

Microsoft-Windows-TerminalServices-SessionBroker-Client

User %1\%2 will be logged on to the local redirector machine (assuming TS Farm scenario). Sending local IP address to the client in the redirection packet.

Related Management Information

Remote Desktop Session Host

Remote Desktop Services

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft