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:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services
Value: 1 (Decimal)
Then it will work again 🙂
Read more here: