- Create a folder on the root directory of the SQL Server (“DB_path”) “if a local path is used” (on the SQL Server).
- Ensure that all RDS servers are added to the Server pool.
- Before deploying a RD Connection broker HA configuration, Please see the following post: Troubles with Removing RD Connection Broker High Availability
RDCB Security Group
Ensure both connection brokers are in the Connection broker security group.
Ensure that all RDCB Servers have the SQL Server Native Client Installed and configured.
Configure the DNS Round Robin using the IP address’s of the connection Brokers.
Please note that the database folder will created on the SQL server if a local path is used, not on the connection broker.
Ensure that you have the correct SQL Native Client
SQL 2008 R2
If you are using SQL 2008 R2, you will need the following script.
DRIVER=SQL Server Native Client 10.0;SERVER=<name of SQL server>;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;Database=<name of database>
If you are using SQL 20012, you will need the following script.
DRIVER=SQL Server Native Client 11.0;SERVER=<name of SQL server>;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;Database=<name of database>
Once the install is complete, the Certificates for SSO and publication will need to be changed to the HA DNS name.
You can change the active Connection broker under tasks> Set active RD Connection Broker server.
Changing the RDCB HA DNS Alias
If you want to change the DNS name, you would need to run the following command as this can only be done in PowerShell.
Set-RDClientAccessName -ConnectionBroker <ACTIVE MANAGEMENT SERVER NAME> -ClientAccessName <NEW DNS RR NAME>
You cannot edit this in the GUI.
Configuring RD Gateway for RDCB HA
Once you have configured HA you will need to create a CAP and RAP for the HA configuration.
Add both connection brokers and the HA DNS Name.
Restart all RDS Servers once the configuration is complete.
- Step 1 – Create Active Directory Group for Connection Brokers (Domain\”Connection Broker AD User Group”) Add Both Connection Broker 01/02/”03 in RDS2016″)
- Step 2 – Add the Connection broker group to the SQL Instance used for the RDCB DB – (Security/Logins/add-account) grant
- Step 3 – Add SQL permissions for the user Group ((Domain\”Connection Broker AD User Group”) dbcreator for the SQL Instance
- Step 4 – Install the SQL Native Client (ODBC-64 bit) on Connection Broker 01 and configure the SQL instance using (integrated Windows Authentication)
- Step 5 – Run the RDCB HA wizard – Dedicated instance option, HA Name: “HAname.domain” – use the following string: DRIVER=SQL Server Native Client 11.0;SERVER=”SQL_Instance_name”; Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;Database=”Database Name”
- Step 6 – Add the SQL DB path “Drive:\DB_path”
- Step 7 – Complete the Wizard
- Step 8 – On the SQL Instance add dbo permission for the security group ((Domain\”Connection Broker AD User Group”) to the new database (Database Name)
- Step 9 – Run the HA wizard on the RDMS console for the Second Connection broker.
- Step 10 – reboot both connection brokers and test.
- Step 11 – open the RDCB Database and run the script SELECT TOP 10 [Id] ,[Name],[LatestTimeStamp] FROM [“DB_name”].[rds].[ConnectionBroker] to confirm the Connection Brokers are communicating with the SQL Instance. the timestamp should update every 30 seconds (estimate)
SQL Native client link: https://www.microsoft.com/en-gb/download/details.aspx?id=36434