windows remote desktop manager windows 7

It triggers an Active Directory query to check for RDP profile settings: If the server has the RD Session Host Role installed, apply the following registry keys to enable the RCM legacy model. To revert to the earlier (pre-Windows Server 2016) behavior, here's what to do:

However, by default in Remote Desktop Session Host (RDSH) in Windows Server, a full Remote Desktop Session is presented, and the application setup process in the profile doesn't start. In this scenario, you expect the user to be presented with the application in the Remote Desktop Session only.

You do so by using the Local Users and Groups tool in Computer Management. You configure a local user account to start an application during logon.You install Windows Server 2016 with the Remote Desktop Session Host role.For more information about this by-design behavior in Windows Server 2016, see RCM behavior in Windows Server.Īdditionally, consider the following scenario: If you require RCM to query AD DS because you are using the Remote Desktop Services attributes, you must manually enable RCM. Starting in Windows Server 2016, RCM no longer queries the user object in AD DS. This information is displayed in the Remote Desktop Services Profile tab of the users object properties in the Active Directory Users and Computers MMC snap-in. 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 article describes Remote Connection Manager (RCM) and the changes to RCM in Microsoft Windows Server 2016.Īpplies to: Windows Server 2016 Original KB number: 3200967 Changes to RCM

Windows remote desktop manager windows 7