Event ID 1303 — 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.

Event Details

Product: Windows Operating System
ID: 1303
Source: Microsoft-Windows-TerminalServices-SessionBroker-Client
Version: 6.1
Message: Remote Desktop Connection Broker on server %1 failed to get Cluster credentials.


Configure an RD Session Host server farm Kerberos identity

The Remote Desktop Session Host (RD Session Host) server farm Kerberos identity is stored on the Remote Desktop Connection Broker (RD Connection Broker) server. You can configure the RD Session Host server farm Kerberos identity by using Windows PowerShell.

To perform this procedure, you must have membership in the local Administrators group and have the Add workstations to domain user right, or you must have been delegated the appropriate authority.

To configure an RD Session Host server farm Kerberos identity:

  1. On the RD Connection Broker server, click Start, point to Administrative Tools, and then click Windows PowerShell Modules.
  2. Type cd RDS:\ and then press ENTER to switch to the Remote Desktop Services module for Windows PowerShell.
  3. Type cd RDSFarms and then press ENTER.
  4. Type cd farm name where farm name is the name of the RD Session Host server farm on which you want to configure the Kerberos identity.
  5. Type cd KerbIdentity and then press ENTER.
  6. Type Set-Item EnableKerbIdentity 1 -AccountName account and then press ENTER, where account is the user name of the account to be used for the Kerberos identity.


To verify that the RD Session Host server can successfully communicate with the RD Connection Broker server:

  1. On the RD Session Host server, start a new Remote Desktop Services session.
  2. After the session is established, disconnect the session. Do not log off from the session.
  3. On a different RD Session Host server, try to reconnect to your existing session. If you are able to reconnect to the existing session, the RD Session Host server is successfully communicating with the RD Connection Broker server.

Related Management Information

RD Connection Broker Communication

Remote Desktop Services

Community Additions