Event ID 1014 — RD Connection Broker Communication

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: 1014
Source: Microsoft-Windows-TerminalServices-SessionBroker-Client
Version: 6.1
Message: The server failed to retrieve the local computer FQDN.


Join the RD Connection Broker server to the domain

RD Connection Broker requires that the computer hosting the RD Connection Broker role service be joined to the domain. To resolve this issue, you must join the RD Connection Broker server to the domain.

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

To join the RD Connection Broker server to the domain:

  1. On the server that will be hosting the RD Connection Broker role service, click Start, right-click Computer, and then click Properties.
  2. Under Computer name, domain, and workgroup settings, click Change settings.
  3. Click Change.
  4. Select the Domain option, and then type the desired domain.
  5. Click OK, and then click OK again.
  6. Restart the computer.

If the problem persists, ensure that the fully qualified domain name of the computer does not exceed 128 characters.


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.

RD Connection Broker Communication

Remote Desktop Services