Windows 10: Event ID 802: RD Connection Broker failed to process

​

After setting up Remote Desktop Quick Start, when some Windows users tried to RDP to the RD Server, they received an error stating that Can’t connect to the remote computer. After probing about the error in Event Viewer, they see Event ID 802: RD Connection Broker failed to process has been registered message. In this post, […]

This article Event ID 802: RD Connection Broker failed to process first appeared on TheWindowsClub.com.

read more...

 

Connection broker high availability

Dear Server Question



Hope you are doing great, I am aware of the present situation is that you need to implement high availability setup for Connection Broker without using SQL database.



With great effort of inquiry, SQL server are beyond the supported scope of community, I can say with doubtless that your knowledge will be broader than mine in this regard.

However, according to the Microsoft documentation, you can deploy a Remote Desktop Connection Broker (RD Connection Broker) cluster to improve the availability and scale of your Remote Desktop Services infrastructure. You can use Azure SQL Database instance or SQL Server in your local environment as the database for the Connection Broker. But you need to find the connection string for the database and make sure you have the correct ODBC driver. See the documentation below:

Add an RD Connection Broker server to configure high availability in RDS | Microsoft Learn



Alternatively, you can set up RDS without Connection Broker for a single-server installation, or configure a high availability Connection Broker deployment that uses dedicated SQL Server. However, these methods may have some drawbacks, such as limited scalability, performance issues, or increased complexity. See the documentation below:

Remote Desktop service (RDS) Connection Broker or Remote Desktop Management service (RDMS) fails - Windows Server | Microsoft Learn



Additionally, I could not find any information about using a batch process to copy the database of Connection Broker 1 to Connection Broker 2, or using any other database instead of SQL database. It seems that these options are not supported or recommended by Microsoft.



For the most appropriate community for posting your issue shall be SQL Server - Microsoft Q&A, which it is a professional place consist of many technical experts or advanced users like you. Moreover, I will keep this thread opened in case our MVP/Volunteer moderator/ can have some targeted insights for you.



Best regards,



Chandy | Microsoft Community Support Specialist

-----------------------

* Your patience and cooperation are highly appreciated.

 

How do i specify the RD Connection Broker Serer in Windows 10 1809

I have the same issue,

If instead of making this Windows 10 1809 box a RDS license server can i point it to an actual RDS License server on Windows server 2012/2016/2019 already running on our network, from with in local Group Policy Editor? "Configure RD Connection Broker server
name" located in Administrative Templates - Windows Components - Remtoe Desktop Services - Remote Desktop Session Host - RD Connection Broker

Is that all that's needed to make this message go away and RDS Licensing Services to continue running after 120 days?

TY in advance!

 

Bluetooth fails to connect, Event ID 16

All devices fail to connect to bluetooth. In event viewer I see Event ID 16 for the BTHUSB source: The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (xx:xx:xx:xx:xx:xx) failed.

I've tried updating, rolling back, uninstalling/reinstalling the drivers, disabling/reenabling bluetooth via the bios, sfc /scannow, and cleaning the registry for the addresses listed. The bluetooth is integrated into the motherboard (ASUS ROG b550-f (Wi-Fi)), I've also used an external usb bluetooth dongle and am getting the same error....

I also tried everything listed in this forum thread here but to no avail.

I'm running win10 pro 21H2 x64.