Win 2016+2019: Remote Desktop Services attributes of ENVIRONMENT tab of a users object properties in AD DS are not applied

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:

Changes to Remote Connection Manager in Windows Serverchanges-to-remote-connection-manager-in-windows-server

 

20 Comments

  1. Conrad Noche

    Do you have to delete the profile on the rdshost first and then apply the registry entry?

    Reply
    1. Martin (Post author)

      No – that is not neccessary 😉

      Reply
  2. Joost Brenters

    Is it also applicable to Windows 2012 R2 with latest patches on AD Controller and RDS hosts (june 2020)?

    Reply
    1. Martin (Post author)

      No., this behavior is changed since 2016 🙂

      Reply
  3. Gabriel Kaplan

    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?

    Reply
    1. Martin (Post author)

      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
      🙂

      Reply
  4. Ricardo Augusto

    Dont work in server 2019

    Reply
    1. Martin (Post author)

      Yes it does! 🙂 – What is your issue?

      Reply
      1. Chris

        Not working for me either

        Reply
        1. Martin (Post author)

          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

          Reply
  5. Nigel

    This was helpful! thank you.

    Reply
  6. Mr. Lucas

    This solution worked with me. Thank you so much for your best solution, it made saving lot time.
    Have a nice day

    Reply
    1. Martin (Post author)

      Thanks – you too 🙂

      Reply
  7. Chris DeRusseau

    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?

    Reply
    1. Martin (Post author)

      Hi Chris,

      No – it should run just right away 🙂

      Best regards Martin

      Reply
  8. Basilio

    Hi, works for me on Server 2016 Workgroup.

    Thanks Martin!

    Reply
  9. César

    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

    Reply
    1. Martin (Post author)

      Hi,

      have not tried on Server 2022 – sorry

      Best regards
      Martin

      Reply
  10. Frank

    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

    Reply
    1. Martin (Post author)

      Hi, yes, regarding the article. But regarding your “end session” you need to create a GPO 😉
      Best regards
      Martin

      Reply

Leave a Reply to Martin Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close