Rds Broker Domain Controller

Anyone who wishes to deploy rds on the domain controller needs to be aware that the connection broker role cannot be installed on the dc.

Rds broker domain controller. Because the wid cannot start the connection broker role service install fails and the install has to be rolled back. Once you have confirmed and selected restart. The installation will fail.

Click the add rd licensing server button. Rds will then start to install. Select a server click the domain controller and click the add button.

Log in rdcb server manager collection properties screenshot captured from rds 2012 group policy. Navigate to remote desktop services and click on the. Go to server manager select add roles and features then select remote desktop services installation.

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. For this tutorial we are going to use the domain server as our rd licensing server but to easily install that role we can add an additional server to the server manager. By default it uses the wid windows internal database.

It was not supported to combine remote desktop services role services and active directory domain services role on windows server 2012 rtm. As you can see the deployment is missing a rd gateway server and a rd licensing server. The connection broker service requires a sql database to store its data.

Add the secondary server by right clicking on the all servers choosing add servers and then picking the server from active directory. This typically only occurs when the rds server is also a domain controller. Confirm selections click add.