The Remote Desktop Connection Broker service on Local Computer started and then stopped 2022
Thủ Thuật Hướng dẫn The Remote Desktop Connection Broker service on Local Computer started and then stopped Chi Tiết
You đang tìm kiếm từ khóa The Remote Desktop Connection Broker service on Local Computer started and then stopped được Update vào lúc : 2022-02-22 10:10:01 . Với phương châm chia sẻ Bí quyết Hướng dẫn trong nội dung bài viết một cách Chi Tiết Mới Nhất. Nếu sau khi Read nội dung bài viết vẫn ko hiểu thì hoàn toàn có thể lại Comments ở cuối bài để Mình lý giải và hướng dẫn lại nha.
RDS Connection Broker or RDMS fails after you disable TLS 1.0 in Windows Server
Is this page helpful?
Yes
No
Nội dung chính
- RDS Connection Broker or RDMS fails after you disable TLS 1.0 in Windows Server
- Is this page helpful?
- In this article
Remote Desktop Connection Broker (TSSDIS) not starting
Answers
All replies
Question
0
Sign in to vote
Hi.. we cannot get the remote desktop services to operate properly.. the error listed above seems to be the issue. No remote users can login. This issue just happened after a quickbooks update and required reboot of the server. When I
try to manually restart the service, the same error message appears. When I try to view the current RDS configuration it says that a remote desktop deployment does not exist in the server pool? Please help as we are down and cannot operate.
Thank you for any help!
Tuesday, September 18, 2022 7:46 PM
0
Sign in to vote
Hi,
> This issue just happened after a quickbooks update and required reboot of the server.
If problem happens after the change, please try to undo the change and re-start your system again to check the result.>When I try to manually restart the service, the same error message appears.
Please open CMD and type “sfc /scannow” to check/repair system files.Use the System File Checker tool to repair missing or corrupted system files:
https://tư vấn.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-systemBesides, open Run, type services.msc and end with enter:
1. Find Remote Desktop Connection Broker service.
2. Right click to open its Properties.
3. Select to Log On tab, please make sure it has been configured to Log on use account Network Service.
4. Select to Dependencies tab, make sure the depending services are running now.Try to manually re-start the service again to check the result. If this RD CB service has been successfully re-started, then, open Server Manager – Remote Desktop Services, confirm that if deployment has been displayed.
Best Regards,
Eve WangPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
.
Marked as answer by
wlarkin-cmx
Wednesday, September 19, 2022 6:35 PM
Wednesday, September 19, 2022 6:08 AM
0
Sign in to vote
Hi,
> This issue just happened after a quickbooks update and required reboot of the server.
If problem happens after the change, please try to undo the change and re-start your system again to check the result.>When I try to manually restart the service, the same error message appears.
Please open CMD and type “sfc /scannow” to check/repair system files.Use the System File Checker tool to repair missing or corrupted system files:
https://tư vấn.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-systemBesides, open Run, type services.msc and end with enter:
1. Find Remote Desktop Connection Broker service.
2. Right click to open its Properties.
3. Select to Log On tab, please make sure it has been configured to Log on use account Network Service.
4. Select to Dependencies tab, make sure the depending services are running now.Try to manually re-start the service again to check the result. If this RD CB service has been successfully re-started, then, open Server Manager – Remote Desktop Services, confirm that if deployment has been displayed.
Best Regards,
Eve WangPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
.
Marked as answer by
wlarkin-cmx
Wednesday, September 19, 2022 6:35 PM
Wednesday, September 19, 2022 6:08 AM
0
Sign in to vote
Thanks for your reply.. I was mistaken, it was Windows Updates (not Quickbooks as I though was stated) that had just recently been installed. I was able to start the Remote Desktop Connection Broker Services by signing in as the Administrator instead
of a user with administrative privileges. Now, everything is working as it should.. my guess is that somehow the Windows Update turned off the Connection Broker service and did not re-enable it. Thanks for your help! -Bill
Wednesday, September 19, 2022 6:35 PM
0
Sign in to vote
Hi,
I am glad to hear that your issue was successfully resolved. If there is anything else we can do for you, please feel không lấy phí to post in the forum.
Best Regards,
Eve WangPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
.
Thursday, September 20, 2022 1:51 AM
0
Sign in to vote
We ran into the same issue. We have a farm of 5 rdp servers and had started preparation for ha setup, with central sql server database hosting rdcms. In our case the root cause was the sql server. The rdcms database translog partition was full. The result
was, that the service could not start. Without any error message.
Friday, August 30, 2022 11:54 AM
Any additional feedback?
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.
Thank you.
In this article
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 2022, Windows Server 2012 R2
Original KB number: 4036954
Remote Desktop Connection Broker (TSSDIS) not starting
Archived Forums
>
Remote Desktop Services (Terminal Services)
Answers
All replies
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 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 14:41 UTC
Its running on the network service account
0
· · ·
Serrano
OP
Rhys Hudson
Jul 11, 2014 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 11:44 UTC
HD IT Solutions is an IT service provider.
Has the server been dcpromoed?
0
· · ·
Serrano
OP
Rhys Hudson
Jul 15, 2014 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 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 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 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 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 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 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 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 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 20:13 UTC
Any other ideas on this?
0
· · ·
Serrano
OP
Best Answer
Rhys Hudson
Aug 19, 2014 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.
Reply
9
0
Chia sẻ
Chia Sẻ Link Tải The Remote Desktop Connection Broker service on Local Computer started and then stopped miễn phí
Bạn vừa đọc tài liệu Với Một số hướng dẫn một cách rõ ràng hơn về Review The Remote Desktop Connection Broker service on Local Computer started and then stopped tiên tiến và phát triển nhất và Share Link Cập nhật The Remote Desktop Connection Broker service on Local Computer started and then stopped Free.
Giải đáp vướng mắc về The Remote Desktop Connection Broker service on Local Computer started and then stopped
Nếu sau khi đọc nội dung bài viết The Remote Desktop Connection Broker service on Local Computer started and then stopped vẫn chưa hiểu thì hoàn toàn có thể lại phản hồi ở cuối bài để Admin lý giải và hướng dẫn lại nha
#Remote #Desktop #Connection #Broker #service #Local #Computer #started #stopped