Remote Desktop Connection Broker stopped

Remote Desktop Connection Broker not starting after reboot

Archived Forums

>

Remote Desktop Services (Terminal Services)

• Question

• 0

  Sign in to vote

  Hi,

  I have recently set up a number of new Server 2016 Remote Desktop Servers. I have a timed script which runs at 6am to reboot them all, as we have some Excel add-ins which have tendency to crash and require a reboot, and a scheduled reboot means the servers don't have to be checked regularly for this.

  I've always done this with the previous Remote Desktop Server (2012 R2), and never had any issues. With the new ones, most of them are fine but on two of them there is an intermittent problem (at least 1 in every 2 days) of them being inaccessible by RDP after the reboot. When I go into thm via VMWare, I can see that the Remote Desktop Connection Broker (Tssdis) service is stopped. If I manually start the service, or reboot the server again, it's then fine.

  I can't replicate the problem manually - if I copy the line from the batch file which reboots all the Remote Desktop Servers and use it to reboot one of the problem ones from a command prompt, they are fine.

  I've checked the event log, and on both of them there's a information item saying that the service has started after the reboot, as would be expected - but then another one saying it has stopped a few seconds later.

  Anyone able to suggest anything? At the moment I'm checking these two servers before most of our staff start work, and starting the service if it's stopped - but this isn't a long-term solution!

  Thanks

  ---

  David

  Friday, January 25, 2019 9:43 AM

All replies

• 0

  Sign in to vote

  Hello David,

  1. Have you compared if any third party tools difference between problematic machine and the working one?

  2. Please try to disable the third-party services in startup: Open Taskmanager--->Go to Start up--->Disable third-party service and leave MS only.

  3. Besides, please also swift the start method of Connection Broker with following steps:

  Right click start button and choose Run

  Type in Services.msc and locate Connection Broker, edit properities.

  Switch between Automatic and Automatic (delayed start) and please also ensure the relavant services(under dependencies tab) are listed in startup.

  Hope above will be helpful.

  Thanks,

  Jenny

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact .

  Monday, January 28, 2019 7:59 AM

• 0

  Sign in to vote

  regedit then
  
  "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control"
  
  Edit- New- DWORD Value
  
  ServicesPipeTimeout
  
  Decimal - Value Data enter 60000
  
  restart
  
  if not worked

  run

  cleanmgr.exe

  if not fixed run

  sfc /scannow

  
  
  • Edited by Dufani Thursday, September 26, 2019 2:40 AM

  Friday, September 13, 2019 2:16 PM

Remote Desktop Connection Broker on 2016 Server

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?

remote-desktop-serviceswindows-server-2016

Comment

Comment Show 0

Comment

5 |1600 characters needed characters left characters exceeded

▼

• Visible to all users
• Visible to the original poster & Microsoft
• Viewable by moderators
• Viewable by moderators and the original poster
• Advanced visibility

Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DSPatrick answered • Oct 20, '20 | DSPatrick edited • Oct 20, '20

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--

Comment

Comment Show 0

Comment

5 |1600 characters needed characters left characters exceeded

▼

• Visible to all users
• Visible to the original poster & Microsoft
• Viewable by moderators
• Viewable by moderators and the original poster
• Advanced visibility

Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JennyYan-MSFT answered • Oct 21, '20 | JennyYan-MSFT commented • Oct 26, '20

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.

1. 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

Comment

Comment · Show 2

Comment

5 |1600 characters needed characters left characters exceeded

▼

• Visible to all users
• Visible to the original poster & Microsoft
• Viewable by moderators
• Viewable by moderators and the original poster
• Advanced visibility

Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ElyseProctor-6655 · Oct 21, 2020 at 08:57 PM

1. Yes, she could not login as a user and I could not login as an admin.

I checked the event logs -
Under TerminalServices-RemoteConnectionManager at the time of the reboot it said 'Remote Desktop Services Network Fair Share was disabled for the user account techni\Administrator.' (Event ID 20487)
Under TerminalServices-LocalSessionManager at that same time it said 'Remote Desktop Services: Session logoff succeeded' (Event ID 23)

0 Votes 0 ·

JennyYan-MSFT ElyseProctor-6655 · Oct 26, 2020 at 09:24 AM

Hi,
For the error message of "'Remote Desktop Services Network Fair Share was disabled for the user account techni\Administrator", please check the value of registry key of
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TSFairShare\NetFS
EnableFairShare

Reference link:
https://www.ryslander.com/disable-fair-sharing-in-windows-server/

Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.

---

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

Thanks,
Jenny

0 Votes 0 ·

DSPatrick answered • Oct 21, '20

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--

Comment

Comment Show 0

Comment

5 |1600 characters needed characters left characters exceeded

▼

• Visible to all users
• Visible to the original poster & Microsoft
• Viewable by moderators
• Viewable by moderators and the original poster
• Advanced visibility

Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

14 Replies

· · ·

Datil

OP

Gregory H Hall

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Jul 8, 2014 at 14:01 UTC

DataGuys is an IT service provider.

What accounts are the services running under... Did anyone change passwords?

0

· · ·

Serrano

OP

Rhys Hudson Jul 8, 2014 at 14:41 UTC

Its running on the network service account

0

· · ·

Serrano

OP

Rhys Hudson Jul 11, 2014 at 11:14 UTC

I need help with this ASAP!!!!

0

· · ·

Mace

OP

Huw3481

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Jul 15, 2014 at 11:44 UTC

HD IT Solutions is an IT service provider.

Has the server been dcpromoed?

0

· · ·

Serrano

OP

Rhys Hudson Jul 15, 2014 at 11:46 UTC

yep old server has been decommissioned and is off.

0

· · ·

Mace

OP

Huw3481

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Jul 15, 2014 at 12:08 UTC

HD IT Solutions is an IT service provider.

So the new server that's running the CB role has been promoted to a DC?

0

· · ·

Serrano

OP

Rhys Hudson Jul 15, 2014 at 12:10 UTC

Yep. What do you mean by CB? but yes its sole DC with global catalog

0

· · ·

Mace

OP

Huw3481

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Jul 15, 2014 at 19:31 UTC

HD IT Solutions is an IT service provider.

Connection Broker.

Unless I'm missing something, MS say that's not supported on any AD DS server - but you can try completely removing the role, restarting and then readding it.

0

· · ·

Serrano

OP

Rhys Hudson Jul 15, 2014 at 21:05 UTC

I can do but will that mess up with the SBS system? Thats why its on a DC. The server is SBS2011

0

· · ·

Serrano

OP

Rhys Hudson Jul 25, 2014 at 22:37 UTC

So I have figured it out that an update may be causing it. (KB2546250) I tried to talk to microsoft and they wanted £400 before even looking at it. The update will not uninstall and the KB article says once installed it cannot be removed. Any ideas here?

Thanks guys. At least spiceworks dont charge £400!!! :)

0

· · ·

Datil

OP

britv8 Jul 26, 2014 at 00:45 UTC

So did you read these? sounds like a rights issue

http://technet.microsoft.com/en-us/library/ee890985(v=ws.10).aspx

Also this

http://social.technet.microsoft.com/Forums/windowsserver/en-US/35abf74f-cdc9-4052-95be-fd01ee42dca2/...

Basically check Session who/what belongs to the Broker Computers group.

0

· · ·

Serrano

OP

Rhys Hudson Jul 26, 2014 at 09:11 UTC

They don't really apply and have already tried it. Thanks for the suggestion though. Any more?

0

· · ·

Serrano

OP

Rhys Hudson Jul 30, 2014 at 20:13 UTC

Any other ideas on this?

0

· · ·

Serrano

OP

Best Answer

Rhys Hudson Aug 19, 2014 at 14:08 UTC

In the end I compared services in remote desktop to another SBS server and removed the excess. It now works.

0

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

RDS Connection Broker or RDMS fails after you disable TLS 1.0 in Windows Server

This article provides methods to make sure Remote Desktop service (RDS) Connection Broker and Remote Desktop Management service (RDMS) can work as expected.

Applies to: Windows Server 2016, Windows Server 2012 R2
Original KB number: 4036954

Symptoms

Assume that you use the inbox Windows Internal Database (WID) in Windows Server. If you disable Transport Layer Security (TLS) 1.0 when you configure security settings, you experience the following issues:

• The Remote Desktop service (RDS) may fail.

• An existing RDS deployment that uses Remote Desktop Connection Broker and WID may fail.

• The Remote Desktop Management service (RDMS) doesn't start.

• You receive the following error message when you try to start the RDMS:

  The Remote Desktop Management service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

• The Remote Desktop Connection Broker role can't be installed.

The Remote Desktop Connection Broker service on Local Computer started and then stopped 2022

Sao chép