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
I opened RDMS and got 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…”
What? I am using RDMS located ON the RD Connection Broker server! Argh!
Well, my first reaction was a reboot. No luck.
I opened Services.msc and noticed that the Remote Desktop Management service was not running. I tried to start it but it failed to start.
Now its time to look deeper. Here is the fix:
I connected to the RDMS database in SQL Server Management Studio, and found the RDCms database in “Pending Recovery” mode.
I took the database offline (Right click the RDCms database, and choose Tasks > Take Offline)
Then I attempted to bring it online and I got this message:
I waited a minute and then attempted to bring the database online again. It came online.
In Services, Remote Desktop Management Service will now start up.
And we are cooking with gas again:
