In the last post we setup the two RDS server that will be used for RD web access, connection broker and sessions hosts. In this post we will go through setting up RD connection broker HA to give more resilience to the RDS deployment.
To add connection broker HA we need to have server with SQL 2008 R2 or above and have a load balancer or DNS round robin to redirect traffic. I am using SQL 2014 with just the database engine and management tools selected. I have used a separate SQL server / RDS licensing for this as I don’t want the database on either of the current RDS servers.
I am going to use DNS round robin for redirecting traffic to both brokers as I don’t have a load balancer setup so I setup the below 4 DNS records on my internal DNS server
Once the database server is setup we need to create a security group and add the two RDS server that will be used as connection brokers.
Once this group has been created we can set up the SQL permissions. Open SQL management studio on the database server and create a new login for the group
Give dbcreator access as this will be required when setting up the HA deployment
To connect to the database SQL Server Native client is require on both the RD connection brokers. The latest version of this client is from SQL 2012 and can be downloaded from Microsoft : https://www.microsoft.com/en-us/download/details.aspx?id=50402
Once the client is installed go to Control Panel\All Control Panel Items\Administrative Tools and go to ODBC Data Sources (64-bit). Click Add and select SQL Server Native Client 11.0
Enter in a Name, Description and SQL server that the permission where setup for the security group above
Leave as integrated windows authentication
Make sure that the application intent is readwrite the rest of the setting can be left as default
Once completed run a test to make sure that the database can be accessed
Once this is completed on both RD connection brokers we can start to set up the HA deployment.
Go back to the RDS deployment page and right-click on RD connection broker and click Configure High Availability
Database connection string: (We need to put in SQL server name & the database name that will be created during the deployment.)
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>
Folder to store database files: (I used the default SQL location)
Add in DNS Name: HARDSBroker.Lab.local
Next page is just to confirm all the settings are correct
Once HA has been configure we can now add the additional connection broker. Right click on RD connection broker and click Add RD Connection Broker Server
Select the required server
Once completed both server should now show the RD Connection Broker role as installed.
In part 3, we will go over creating and configure RDS collections