High Availability Connection Broker killed RDS Install

Question

I followed Microsofts directions for High Availablity

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-connection-broker-cluster

It broke my install.

I followed the directions exactly. Microsoft fails to help with this part.

What do I do?

Help

Answer 1

After many many issues I finally figured out the issues.

There are so many with RDS. It's a 'cluster' :) of issues that pop up one after the other.

Things I did to get it working:

After adding high availability I started getting the error. Maybe restarting the system right away would have cured that but I didn't do that.

I had added a system right after and thats when I started getting issues.

Ultimately I had to be on the server I wanted to add to high availability. Like I'm on CB02 and adding.
Add-RDServer -ConnectionBroker "CB01" -Server "CB02" -Role RDS-CONNECTION-BROKER

I initially had another Connection Broker CB00. I had Remove-RDServer the role after adding the role to CB01 and moving the ActiveMangementServer. The error kept coming back.

1. I had to go to CB00 and manually remove RDS services and restart. Through "Remove Roles and Features"
2. I had to go into the High Availability Database that had been created and remove CB00 from the list of Brokers.
   delete from [RDSConnectionBroker].[rds].[ConnectionBroker] where Name = 'CB00'

Answer 2

I'm having to rebuild everything. Now I really don't trust the setup process. Scary how quickly my setup went downhill from trying to setup redundancy. It's a shame Microsoft makes it hard to understand.

Answer 3

I have finally discovered my mistake.

I had used a licensing server that had a Connection Broker installed on it for this implementation. The license server was supposed to be shared. So now I need to remove Connection Broker from that RDS implementation so we can use the license server.

So the error was accurate but not very helpful in WHAT was wrong.

Answer 4

Hello there,

From memory if you are not using connection broker high availability the connection broker will retain information in the Windows Internal Database. 

If the session host servers etc were not removed correctly then it wouldn't have removed the entries from the database. 

Try the below script and see if that helps.

Set-RDConnectionBrokerHighAvailability `
    -ClientAccessName "rds.contoso.com" `
    -DatabaseConnectionString "DRIVER=SQL Server Native Client 11.0;SERVER=db.contoso.com;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;DATABASE=rdscbha"

You omit the "Folder to store database" or -DatabaseFilePath because, well, it's optional and your MSSQL is already configured on where to store the new databases by default.

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer--