In a previous Wiki article, we ran through the process of setting up HA for the RD Connection Broker in Windows Server 2012.
In this wiki we'll dive a little deeper in the SQL permissions part.
The prerequisite that refers to the SQL permissions is explained by the setup as: “A Microsoft SQL Server with write permissions granted to all RD Connection Broker servers that will be part of the deployment.”
But what exactly does that mean?
When you would not prepare any SQL permissions except opening port 1433 for your RD Connection Broker, you will receive the following error in the wizard:
“The database specified in the database connection string is not available from the RD Connection Broker server <servername>…”
A final FYI to be aware of, if you created a database before starting the RDCB HA wizard the wizard will delete this database and create a new one during the setup.
Freek Berson edited Original. Comment: Added a source link
I can connect to my SQL Cluster instance via powershell from the RDCB VM fine using this connection string:: DRIVER=SQL Server Native Client 11.0;SERVER=DFWWHDB102\APPLICATION;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;DATABASE=VDI
I've deleted the database and told the RDCB HA wizard that same string but it yields the error message stated above. If I remove the instance name, it will clear that screen and go one, but fail to create the database after clicking "configure". Does RDCB HA not support named instances?