The Server Pool Does Not Match the RD Connection Brokers That Are In It
Estimated Reading Time: 1 MinutesThe Server Pool Does Not Match the RD Connection Brokers That Are In It
Working with small and medium sized businesses, we often use the Server Manager’s Remote Desktop Management Services (RMDS) UI to manage RDS deployments. The problem is that this UI is not without issues. We frequently run into problems using this tool. Because it bombs for many reasons, we decided to write a series of blogs posts that detail the problems we run into using RDMS and how to fix them.
RDMS Problem #1: The Server Pool Does not Match the RD Connection Brokers That Are In It
Environment:
- Windows Server 2012 R2 deployment
- One Session Collection
- RD Connection Broker is not in HA mode
You open RDMS and get the message “The Server Pool Does not Match the RD Connection Brokers That Are In It. Errors: 1. Cannot connect to any of the specified RD Connection Broker servers…”
Here is the fix:
Connect to the RDMS database in SQL Server Management Studio,
Open SSMS by using right click, “Run as administrator” and in the database server copy/paste
WID2008
np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
WID2012+
np:\\.\pipe\MICROSOFT##WID\tsql\query
take the database offline (Right click the RDCms database, and choose Tasks > Take Offline)
Then bring it online
In Services, Remote Desktop Management Service will now start up
Still facing the same issue no use after installing also