Share via

RD Connection Broker No letting add servers to an existing collection

Anonymous
2024-03-05T16:44:53+00:00

Our current rds setup consists on 1 broker (it was 2 but one got corrupt and it was removed). One broker (broker01) was working fine, until about 2 weeks ago where it wouldn't let us add any servers to a collection. If we create a new collection, we are able to add the servers (just in the creation moment). Otherwise, we can't.

Also, we tried to add a secondary RD Connection Broker (rebuilt from scratch) and we are unable to add it as well.

The broker is a 2019 server Datacenter (in-place upgrade from 2012 R2). The new broker is also a 2019 Datacenter (built from scratch)

Any help is appreciated it.

Windows Server Remote and virtual desktops Remote desktop services and terminal services

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-03-06T08:32:40+00:00

    Hello,

    Based on the information provided, your issue should be related to the previous second RDCB server.

    Here are some troubleshooting steps you can verify if the previous second RDCB server is completely removed from your RDS environment:

    1. Open Server Manager or the Remote Desktop Services Manager console on any of your servers. Navigate to the Remote Desktop Connection Broker role and look for the list of connection brokers in your farm. If the old RDCB is not listed here, it has been uninstalled or removed from the farm.
    2. The configuration data for Remote Desktop Services is typically stored in a SQL database. Connect to the SQL Server hosting the RDS configuration database and check the tables related to the connection broker (like RDCB_Farm or RDCB_Server) to see if the old RDCB's information still exists.
    3. Use PowerShell commands like Get-RDConnectionBrokerHighAvailability or Get-RDServer to view the current status and members of your RDS farm. If the old RDCB doesn't show up in these commands' outputs, it has been removed.
    4. Examine the Event Viewer logs on both the remaining RDCB server and the one you suspect was removed. Look specifically at the Remote Desktop Services event logs for entries that might indicate the removal or disconnection of the second RDCB server.

    Additionally, you can consider removing and re-adding the RD Connection Broker role on the problematic server to refresh its configuration.

    I hope the information above is useful. If you have any question or concern, please feel free to let us know.

    Regards,

    Jacen Wang

    0 comments