Installing remote desktop services on a domain controller
Written by:
Will Kruss
on
05 June 2023 12:01 PM
|
|
Licenses are per USER for Domain controllers or domain members (unlike workgroup where in 2019 or later only per device is supported) Go to Server Manager Select Add roles and Features, then select Remote Desktop Services Installation. Select the Standard Deployment option Deployment scenario is session NOT VDI. Select the Domain Controller for all services, RD Connection Broker, RD Web Access, and RD Session Host. Select as a session host. Once you have confirmed and selected Restart. RDS will then start to install.
There you have it ….. The Domain Controller now has the Connection Broker, Web Access and Session Host roles. Now set Deployment Properties in the Deployment Overview click 'Tasks' -> Edit Deployment Properties and ensure the licensing it set to per user. Click on RD Licensing to install licensing. Do NOT install gateway that is for web farms. Add the server by clicking the right arrow and click 'Next'. Then click 'Add' to complete.
You then need to create a collection and add the server. To do that click on 'Collections' on the left hand panel. Then click on 'Tasks' (in the Collections window) and choose 'Create Session Collection' Enter any name you like e.g. Collection and click Next Click the right arrow to add the server to the collection and click Next (it may already be added in which case just hit Next) Domain Users will automatically be added, just click Next. UNCHECK Enable user profile disks (very important) and click Next. Click Create. It may show an Invalid Operation error, this can be ignored.
Now click 'Tasks' on the Collections window again and choose 'Edit Deployment Properties' Select 'Do not use an RD gateway server' Check it is in Per user mode for licensing.
Now go to the RD Licensing Manager If there is a yellow warning icon on the server, click 'Review' if required and 'Add to group' where recommended, then restart the Remote Desktop Licensing service. Then refresh in the RD Licensing Manager and it should show a green tick. Double click on the server, then right click on it and choose Manage Licenses. If it says the details are corrupt you need to go to the properties and enter the 'Required Information' fields Then right click and choose 'Manage Licenses' Select 'Rebuild the license server' -> this server is being redeployed Confirm deletion and hit Next Have VPSBlocks staff install licenses using SPLA as per normal. Once complete check the RD Licensing Diagnoser.
!!!! If all settings are correct but running RD Licensing Diagnoser still shows the error about inability to connect to Licensing server, please run as below in PowerShell Administrator elevated window:
NOTE ON UPGRADES FROM PREVIOUS OPERATING SYSTEMS: You then will likely need to redeploy the license server in the license manager. You will need to go to properties and fill out the ownership details (just name and company) otherwise it will say it's corrupt. If you cannot add the server to the collection make sure there are no GPO policies at:
Then run gpupdate Once your collection is created open the licensing and register and license. !! THE LAST RESORT BEFORE REINSTALLATION !! 1. Remove all registry settings at HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services and HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server and HKLM\SYSTEM\CurrentControlSet\services\TermService 2. Set all group policy settings to unconfigured Computer Configuration\Policies\Administrative Templates\Windows Components\Terminal Services or Remote Desktop Services | |
|