Hello,
I'm attempting to setup an RemoteApp environment on AWS using EC2 instances for the Server Roles and an AWS RDS SQL Instance for my Connection Broker HA SQL Database.
I know this kind of setup works for Azure SQL Databases, as the step by step walkthrough here shows using the managed SQL Instances in Azure to hold the RD Connection Broker DB:
https://blogs.technet.microsoft.com/hybridcloudbp/2016/11/15/new-rds-capabilities-in-windows-server-2016-for-service-providers/
In there it shows creating the SQL DB and using a Database User account to authenticate the connection brokers to the SQL DB rather than the usual Domain Group containing the connection broker computer accounts. The link doesn't go into much detail about
the permissions needed in the database or even show the complete connection string used.
When I try the same setup in AWS with their RDS SQL Instances I have had quite a few challenges getting it working.
List of issues I encountered:
- Since the required permissions on the SQL Database are not discussed in the walk through I had to guess what permissions to grant. After much trial and error we determined we have to grant our SQL Account SetupAdmin permissions, create the DB manually,
then grant the SQL user DB Owner rights on the database
- Links on the web discuss using both the SQL ODBC 13 driver as well as the SQL Native Client 11, I tried using both with the same results.
- During the install you select the shared database option which requires a connection string to login as the SQL user. To validate the connection string is working we create a UDL file, set the provider to ODBC for SQL and enter the string in the Connection
String box. We only used strings that were able to login to the AWS SQL Instance from BOTH Connection Broker servers.
Here's where it gets weird...
I'm able to add the connection broker HA configuration to the first connection broker with no issues. This works in both the Server Manager GUI as well as when using the New-RDSessionDeployment cmdlet.
However, when you go to add additional connection brokers you get the following error message:
![RD CB HA Error]()
This issue occurs no matter which of my two connection broker servers is added to the deployment first. The first broker added to the deployment with HA works, the second is unable to be added to the deployment
These servers have no other roles installed on them and are wholly dedicated to being connection brokers.
I have verified the SQL Port and all other ports are open between the Connection Brokers and the SQL Instance
I have verified the connection string works to connect to SQL from both connection brokers when using a UDL file to test the connection.
During an attempt to add the second connection broker I watched the SQL Logs and saw no failed logins or anything else of note
A SQL trace shows no TSQL is being sent to the RDSFarm database during the attempt to add a connection broker.
I put Wireshark on the second connection broker and can see NO
connection attempt being made from that connection broker to SQL. This leads me to believe the issue is not related to my connection string, networking or SQL permissions.
I have redeployed this RDS Deployment using the dedicated SQL Server option pointed to an EC2 SQL server and with no changes to the connection brokers I'm able to add additional Connection Brokers without issues.
The best unsubstantiated guess I have is it's trying to use the Dedicated SQL Server option due to it asking about the computer accounts being a member of the RDS Management local group on the SQL Server. That is the only suggestion in the error I can't
do on the AWS SQL Instance since we don't have access to the underlying OS, but I would think the same is true for Azure SQL.
What I don't understand is how it could be failing to login to SQL with the connection string when everything seems to indicate no connection attempts are being made!
I've run out of ideas at this point and I'm hoping someone can get me back on the right track.