Issues with Remote Desktop Connection Broker High Availability on Windows Server 2016

Question

Hi all,

I'm having troubles configuring RD Connection Broker High Availability on Windows Server 2016.

The initial setup on the first Connection Broker worked well, using a shared database server configuration. I am following steps outlined in this guideline: rds-connection-broker-cluster

However, if I'm now trying to add the second Connection, I receive the error message down below. When setting up an ODBC data source on the affected Connection Broker server, using the very same settings from the Connection String I used in the HA-Setup, the connection to the SQL Server and database works just fine, so it's neither a connectivity/firewall issue, nor authorization issue.

Any idea, what I might missing?

Thanks,

Harald

Answer 1

Hello @Niehus, Harald (GE Renewable Energy)

I deployed my RDCB HA environment according to this article: Remote Desktop Services 2016, Standard Deployment – Part 6 – RD Connection Broker High Availability .

Please check the prerequisites mentioned:

• Be sure to add second connection broker to All Servers in Server Manager (on your primary RDCB) so that you can manage it from there.
• Create Active Directory Security Group and add all your Connection Broker servers to it. We need this group to be able to convert the RD Connection Broker to a highly available RD Connection Broker.
• Configure the DNS Round Robin using the IP address’s of the Connection Brokers.
• SQL server is a must. I will run this on SQL 2016. Be sure to pre-create a folder to store the SQL database files on SQL server if you are not planning to use SQL default path. Give RD Connection Brokers full access on the folder.
• Ensure that all RDCB Servers have the SQL Server Native Client Installed

Best Regards
Karlie

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.