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”.
#Parallels client 516 error install
Step 4 – Install the SQL Native Client (ODBC-64 bit) on Connection Broker 01 and configure the SQL instance using (integrated Windows Authentication).Step 3 – Add SQL permissions for the user Group ((Domain\”Connection Broker AD User Group”) dbcreator for the SQL Instance.Step 2 – Add the Connection broker group to the SQL Instance used for the RDCB DB – (Security/Logins/add-account) grant.Step 1 – Create Active Directory Group for Connection Brokers (Domain\”Connection Broker AD User Group”) Add Both Connection Broker 01/02/”03 in RDS2016″).Restart all RDS Servers once the configuration is complete. Once you have configured HA you will need to create a CAP and RAP for the HA configuration.Īdd both connection brokers and the HA DNS Name. Set-RDClientAccessName -ConnectionBroker -ClientAccessName If you want to change the DNS name, you would need to run the following command as this can only be done in PowerShell. You can change the active Connection broker under tasks> Set active RD Connection Broker server. Once the install is complete, the Certificates for SSO and publication will need to be changed to the HA DNS name. DRIVER=SQL Server Native Client 11.0 SERVER= Trusted_Connection=Yes APP=Remote Desktop Services Connection Broker Database= If you are using SQL 20012, you will need the following script. DRIVER=SQL Server Native Client 10.0 SERVER= Trusted_Connection=Yes APP=Remote Desktop Services Connection Broker Database= SQL 2012 If you are using SQL 2008 R2, you will need the following script. Please note that the database folder will created on the SQL server if a local path is used, not on the connection broker.Įnsure that you have the correct SQL Native Client SQL 2008 R2 DNS ConfigurationĬonfigure the DNS Round Robin using the IP address’s of the connection Brokers. Before deploying a RD Connection broker HA configuration, Please see the following post: Troubles with Removing RD Connection Broker High AvailabilityĮnsure both connection brokers are in the Connection broker security group.Įnsure that all RDCB Servers have the SQL Server Native Client Installed and configured.Ensure that all RDS servers are added to the Server pool.
0 kommentar(er)
