Remote Desktop Connection Broker on 2016 Server

Question

I have a windows standard 2016 server. An employee of mine remotes into the server to use a certain application - every time the server is rebooted she cannot login with Remote Desktop. I have to go into the server via LogMeIn and go into services and turn on the Remote Desktop Connection Broker. It is already set to be automatic, yet it never starts by itself when the server reboots. Is there some type of fix so that the service will actually start automatically?

Answer 1

Just implemented a work around as I was having random occurrences on 115 servers.
When the connection broker service is stopped and a user tries to RDP, event ID 1296 generated in the event log for the Terminal Services-session Broker-client. I created a scheduled task to Net Start tssdis when Event ID 1296 occurs.
If the RDP connection broker service is stopped, one failed remote connection will kick off the task. RDP will become available in approximately 30 seconds. Subsequent attempts to RDP should be successful.
Not an ideal solution, but the perceived outage time is an attempted connection + 30 seconds.

Answer 2

What's found in the system event log when it fails to start?

--please don't forget to Accept as answer if the reply is helpful--

Answer 3

Hi,
1.every time the server is rebooted she cannot login with Remote Desktop.
Please confirm if this occurred even when you remoted to the server with admin account?

Normally, the Remote Desktop Connection Broker service can stop for many reasons, including:
• The service was stopped by an administrator.
• The service could not allocate the required memory.
• The service was prevented from starting because the user account could not be authenticated.

2. what is the error message when user failed to remote after server reboot?

3.Kindly check if any event logs has captured the problem:
Event log checking:

TerminalServices-RemoteConnectionManager and TerminalServices-LocalSessionManager logs to view information about connections.

Step 1: Press Windows+R to open the Run dialog, enter eventvwr (or eventvwr.msc) and hit OK.

Step 2: Navigate to Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-*

 ----------
Hope this helps and please help to accept as Answer if the response is useful.

Thanks,
Jenny

Answer 4

What's found in the system event log when Remote Desktop Connection Broker fails to start?

--please don't forget to Accept as answer if the reply is helpful--