KnowledgeBase: Remote Desktop Connection Broker cannot co-exist with Active Directory Domain Services role on Windows Server 2012
In Windows Server 2012, the Active Directory team has consciously blocked some Server Roles and Features from coexisting with the Active Directory Domain Services Role. Two months ago, I blogged on the incompatibility between the Fail-over Cluster Feature and the Active Directory Domain Services Role in Windows Server 2012. Earlier, I blogged on the incompatibility between the DirSync Tool and Active Directory Domain Services and Active Directory Federation Services.
Today, because of a new Microsoft KnowledgeBase article, titled Remote Desktop Services role cannot co-exist with AD DS role on Windows Server 2012, the Remote Desktop Services (RDS) Connection Broker can be added to the list of incompatibility with Active Directory Domain Services on the same Windows Server 2012 installation.
When you try to install the Remote Desktop Connection Broker (available as a Role Service for the Remote Desktop Services Role) on a Windows Server 2012-based Active Directory Domain Controller, it will fail rather cryptically. In the event log of this server, however, you will find a more specific error:
Additionally, if you try to promote a Windows Server 2012 installation with the Remote Desktop Connection Broker to an Active Directory Domain Controller, the Remote Desktop Connection Broker may fail and you may receive the following error message:
The server pool does not match the RD Connection Broker that are in it. Errors:
Cannot connect to any of the specified RD Connection Broker servers. Ensure that at least one server is available and the Remote Desktop Management (rdms), RD Connection Broker (tssdis), or RemoteApp and Desktop Connection (tscpubrpc) services are running.
Related KnowledgeBase article
2799605 Remote Desktop Services role cannot co-exist with AD DS role on Windows Server 2012
64bit Directory Synchronization Tool is here
Office 365 Management Portal Directory Synchronization
Active Directory in Hyper-V environments, Part 8