Since Windows server 2016, the attributes of theese tabs, are no longer applied:
This is because Microsoft changed the way it works, and therefore doomed it “legacy RCM”:
This article describes the Remote Connection Manager (RCM) and the changes to RCM in
Windows Server Standard, version 1803, Windows Server Datacenter, version 1803, Windows Server version 1709 and Windows Server 2016.
In Windows Server 2012 R2 and earlier versions, when a user logs on to a terminal server, the RCM contacts the domain controller (DC) to query the configurations that are specific to Remote Desktop on the user object in Active Directory Domain Services (AD DS). This information is displayed in the Remote Desktop Services Profile tab of a users object properties in the Active Directory Users and Computers MMC snap-in.
Starting in Windows Server 2016, RCM no longer queries the users object in AD DS. If you require RCM to query AD DS because you are using the Remote Desktop Services attributes, you must manually enable RCM.
Additionally, consider the following scenario:
-
You install Windows Server Standard, version 1803, Windows Server Datacenter, version 1803, Windows Server version 1709 or Windows Server 2016 with the Remote Desktop Session Host role.
-
You configure a local user account to start an application during logon by using the Local Users and Groups tool in Computer Management.
Luckily, it can be enabled, by adding this, on all your RDS hosts:
Regedit:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services
Name: fQueryUserConfigFromDC
Type: Reg_DWORD
Value: 1 (Decimal)
Then it will work again 🙂
Read more here:
Related Posts
PrintNightmare: Clarified Guidance for CVE-2021-34527 Windows Print Spooler Vulnerability- PrintNightmare: Out-of-band updates ready – patch now!
Windows server 2019: Troubleshoot missing SYSVOL and Netlogon shares
Windows: Give user allow to restart services.- RDS: How to block user access to Windows Update on Windows Server
- RDSFARM: Certificate errors when using .local or similar AD names…and the fix :-)
Do you have to delete the profile on the rdshost first and then apply the registry entry?
No – that is not neccessary 😉
Is it also applicable to Windows 2012 R2 with latest patches on AD Controller and RDS hosts (june 2020)?
No., this behavior is changed since 2016 🙂
Hello, this solution worked perfectly well for me having Active Directory installed
But if AD is not installed it did not work for me, is there any way to solve it in these cases?
HI,
No sorry have none running i Workgroup mode, I only found this:
https://docs.microsoft.com/en-us/troubleshoot/windows-server/remote/remote-connection-manager-changes
🙂
Dont work in server 2019
Yes it does! 🙂 – What is your issue?
Not working for me either
What Windows, 2019? I have set this up on Windows 2019 several times, with no issues.
Are they domain joined, do you type the key case-sensitive?
Regards Martin
This was helpful! thank you.
This solution worked with me. Thank you so much for your best solution, it made saving lot time.
Have a nice day
Thanks – you too 🙂
Does the RDS server need rebooted? I added this and it didn’t map my drive letter from AD. Or does it need to go under terminal Services\Client in the registry?
Hi Chris,
No – it should run just right away 🙂
Best regards Martin
Hi, works for me on Server 2016 Workgroup.
Thanks Martin!
Hi! Doesn´t work in a Windows server 2022 datacenter… After add the registry keys, nothing happens when I log in… Other tips or tricks?
Thanks in advance
Hi,
have not tried on Server 2022 – sorry
Best regards
Martin
Hi, are the settings in AD users and computers session tab affected by this?
On server 2019 “End a disconnected session after 10 minutes” is not working.
Thanks in advance Frank
Hi, yes, regarding the article. But regarding your “end session” you need to create a GPO 😉
Best regards
Martin