Duration: 2:27

41 views

0

Here's how to Fix Event ID 802 RD Connection Broker failed to process on Windows.

i. RD Connection Broker is a role service that provides the following functionality for Remote Desktop Services:

- It allows users to reconnect to their existing sessions in a load-balanced RD Session Host server farm. This means that users can access their applications and data from any RD Session Host server in the farm, without losing their work or settings.
- It provides users access to virtual desktops hosted on RD Virtualization Host servers and to RemoteApp programs hosted on RD Session Host servers through RemoteApp and Desktop Connection. This means that users can access a variety of desktops and applications from a single interface, without installing them on their local devices.
- It manages the configuration and load balancing of the RD Session Host servers in the farm. This means that it can distribute the user sessions across the servers based on their availability and performance, and update the server settings automatically.

RD Connection Broker is an essential component of a Remote Desktop Services infrastructure, as it improves the availability, scalability, and user experience of the remote desktops and applications.

ii. RD Connection Broker is a role service that provides the functionality for Remote Desktop Services, such as reconnecting users to their existing sessions, load balancing the sessions across the servers, and providing access to virtual desktops and RemoteApp programs. However, some common issues that may occur with RD Connection Broker are:

- Communication issues when RD Connection Broker connects to SQL Server. This issue may occur when the Windows Filtering Platform blocks the UDP port 1434 that is required for RD Connection Broker to connect to the SQL Server. You can fix this issue by adding a WFP rule to enable the RD Connection Broker service to use UDP port 1434.
- Installation or launch problems with RD Connection Broker. This issue may occur when the RD Connection Broker role service is not installed or configured properly, or when there are conflicts with other role services or applications. You can fix this issue by uninstalling and reinstalling the RD Connection Broker role service, or by using the Server Manager or PowerShell commands to add or remove the role service.
- Configuration or synchronization problems with RD Connection Broker. This issue may occur when the RD Connection Broker servers in a cluster are not configured or synchronized correctly, or when there are errors in the database or the network settings. You can fix this issue by using the Failover Cluster Manager or PowerShell commands to configure or troubleshoot the cluster settings, or by checking the database connection string or the network firewall rules.