Resolving Azure Virtual Desktop Agent Issue: "Connection not found: RDAgent does not have an active connection to the broker"

Correct Answers: A and C

Error: “Connection not found: RDAgent does not have an active connection to the broker” indicates that your virtual machines may be at their connection limit, so the VMs can't accept new connections.

This issue can be resolved by decreasing the max session limit and increasing the resource capacity of the virtual machines.

Option A is correct.

Decreasing the max session limit will ensure that the resources are more evenly distributed across session hosts and it will prevent resource depletion.

Option B is incorrect.

To resolve the given issue, it is recommended to decrease the max session limit.

Option C is correct.

Increasing the resource capacity of virtual machines will increase the connection limit for the VMs.

Option D is incorrect.

resource capacity of VMs needs to be increased, not decreased.

Option E is incorrect.

Generating the new registration key is not the recommended solution to resolve the issue.

To know more about how to troubleshoot common Azure Virtual Desktop Agent issues, please visit the below-given link:

The error message "Connection not found: RDAgent does not have an active connection to the broker" typically indicates that the Azure Virtual Desktop Agent is unable to connect to the broker service. This could be due to a variety of reasons, such as network connectivity issues or incorrect configuration settings.

To resolve this issue, one potential solution is to generate a new registration key for the VM. This is because the registration key is used to authenticate the connection between the Azure Virtual Desktop Agent and the broker service. By generating a new registration key, you can ensure that the connection is established with the correct credentials.

To generate a new registration key, follow these steps:

1. Log in to the Azure portal.
2. Navigate to the Virtual Desktops service.
3. Click on the "Host pools" tab.
4. Select the host pool that is experiencing the issue.
5. Click on the "Properties" tab.
6. Scroll down to the "Registration info" section.
7. Click on the "Generate new" button next to "Registration key".
8. Follow the prompts to generate a new registration key.

After generating the new registration key, you will need to update the Azure Virtual Desktop Agent on the affected VM to use the new key. This can typically be done by running the following command on the VM:

Set-RdsRegistrationInfo -ConnectionBroker <broker_fqdn> -RegistrationKey <new_registration_key>

In summary, if you encounter the error "Connection not found: RDAgent does not have an active connection to the broker" with Azure Virtual Desktop Agent, one potential solution is to generate a new registration key for the VM and update the Azure Virtual Desktop Agent with the new key.