Unable to Remote Desktop after DC Promo

Question

Hi,

I have a Windows Server 2019 server with Remote Desktop (terminal server). I've recently converted it into a primary domain controller. I know this is not good practice but the client is aware of the risk.

After promoting, I am unable to remote desktop onto the server normally but I can remote using the mstsc /admin. I've checked:

1. Remote Desktop is turned on
2. Turned off Firewall

What I notice is that I get error when adding license which you normally don't.

The licensing mode for remote desktop session host server is not configured when it has. Set to per user.

The event error states this.

Please help. Spent a good 4 hours plus on this.

Answer 1

Hello @Sin Ngo ,

Thanks for your query.

1.What's your RDS roles and environment? You may refer to below link for detailed steps of RDS deployment:
https://nedimmehic.org/2017/01/21/deploying-remote-desktop-services-2016-step-by-step/

2.On your RD Session Host servers, please make sure that the Licensing mode has been configured and the FQDN of your RD Licensing server has been Specified. For RDSH servers that are part of a session collection, you can do this on your broker via Server Manager -- RDS -- Overview -- Deployment Overview -- Tasks -- Edit Properties -- RD Licensing tab.
For RDSH servers that are not part of a collection, you may configure via group policy settings:
Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Licensing\
Use the specified Remote Desktop license servers Enabled
Set the Remote Desktop license mode Enabled
https://social.technet.microsoft.com/Forums/windowsserver/en-US/84a6a21c-9195-43f0-89ac-a7b0cc1f0a0a/event-id-1069-on-windows-2016-server?forum=winserverTS

3.Please try below steps to see if that could resolve:
On the remote session host server, open "Registry Editor" -> find "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod"->right click "Graceperiod"->Permissions-> change the owner of the registry key->delete L$RTMTIMEBO.
https://learn.microsoft.com/en-us/answers/questions/61592/remote-desktop-services-issue-after-installation-f.html

Best regards,
Leila

---

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Thanks for the suggestions.

I tried the 3rd option and it invoke another error.

With further investigations, I renamed the system32\lserver to lserver_old so that it can recreate the license file. I can now reactivate my clients remote desktop license where before, the wizard process would error out.

Using the RD remote licensing diagnoser, it still says the remote desktop session host server is not configured. :(

The licensing mode of "per user" is definitely set correctly.

Checked if it could be a RDS Broker database issue as per the resource link "https://social.technet.microsoft.com/Forums/windowsserver/en-US/8f032597-9eff-4876-8239-fca71b8d118d/rds-broker-database-rdcms-status-quotrecovery-pendingquot-after-reboots?forum=winserverTS"

The RDCms is running fine.

Any other ideas? I'm in the process of trying to fix the group policy management error below. Not sure if its related. This is after the DC Promo from Windows Server 2008 to 2019.

Answer 3

Hello @Sin Ngo ,

Thanks for your information.

Please check if FRS to DFRS migration has an issue regarding GPO migration and try to restore GPO.

https://community.spiceworks.com/topic/2279480-the-processing-of-group-policy-failed
https://learn.microsoft.com/en-us/answers/questions/54025/event-id-1058-processing-of-group-policy-failedwin.html
https://theitbros.com/the-processing-of-group-policy-failed-windows-attempted-to-read-the-file/

Answer 4

I think I'm getting much close now. I fixed the GPO issue by using DCGPOFix command.

Now I can at least log into the server twice as normal. Anymore than 2, it doesn't use the remote desktop licenses of 5.

Error below

Remote Desktop Connection Broker Client failed to redirect the user.
Error: NULL

---

What else could cause that issue?

Answer 5

I have a Windows Server 2019 server with Remote Desktop (terminal server). I've recently converted it into a primary domain controller. I know this is not good practice but the client is aware of the risk.

A much cleaner / safer method would be to install the hyper-v role (as only role) on host, then stand up two virtual machines. One for active directory domain services and other one as the application server with RDS role.

--please don't forget to upvote and Accept as answer if the reply is helpful--