Microsoft Remote Desktop Manager For Windows 10

 admin



-->

Remote Access; Remote Desktop Manager 2021.1.23.0 Remote Desktop Manager (RDM) centralizes all remote connections on a single platform that is securely shared between users and across the entire team. Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2, Windows Server 2016. You can use the Remote Desktop client for Mac to work with Windows apps, resources, and desktops from your Mac computer. Use the following information to get started - and check out the FAQ if you have questions.

This article describes Remote Connection Manager (RCM) and the changes to RCM in Microsoft Windows Server 2016.

Original product version: Windows Server 2016
Original KB number: 3200967

Download DirectX End-User Runtime Web Installer CloseDirectX End-User Runtime Web Installer On the Windows PC you want to connect to remotely, download the Microsoft Remote Desktop assistant to configure your PC for remote access. How to Allow or Prevent Users and Groups to Log on with Remote Desktop in Windows 10 You can use the Remote Desktop Connection (mstsc.exe) or Microsoft Remote Desktop app to connect to and control your Windows 10 PC from a remote device. This remote desktop manager is not only compatible with Windows 10 operating system but also works pretty well on Windows XP, Windows Server 2003 and Windows 7 etc. However, if you want to use this Windows remote desktop connection tool on Windows XP make sure that you are having the latest version of this tool.

Changes to RCM

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 the users object properties in the Active Directory Users and Computers MMC snap-in.

Starting in Windows Server 2016, RCM no longer queries the user 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. For more information about this by-design behavior in Windows Server 2016, see RCM behavior in Windows Server.

Additionally, consider the following scenario:

  • You install Windows Server 2016 with the Remote Desktop Session Host role.
  • You configure a local user account to start an application during logon. You do so by using the Local Users and Groups tool in Computer Management.

In this scenario, you expect the user to be presented with the application in the Remote Desktop Session only. 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.

To revert to the earlier (pre-Windows Server 2016) behavior, here's what to do:

If the server has the RD Session Host Role installed, apply the following registry keys to enable the RCM legacy model. It triggers an Active Directory query to check for RDP profile settings:

  • Path: HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services and HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStations<Winstation name>
  • Name: fQueryUserConfigFromDC
  • Type: Reg_DWORD
  • Value: 1 (Decimal)

Then, restart the Remote Desktop Service. If the server doesn't have the Remote Desktop Service role installed, you must set up an extra registry key:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server

More information

When a user logs on to an RDSH server, the attributes on the Remote Desktop Services Profile tab of the users object properties in AD DS aren't applied to the user. The user's attributes aren't enforced, and everything is working as designed. So, no warning is generated, and no event is logged.

For example, if you use the RDS attributes to specify a Remote Desktop roaming profile, users won't load that profile. They will use a local profile instead. In this situation, there are no error message or logged events. You can only know whether the user profile isn't the RDS roaming profile in one of the following ways:

Connection
  • You notice that the desktop environment isn't the expected layout.
  • You view the profile types in the system Control Panel applet.

Remote Desktop Services Profile tab in Active Directory Users and Computers:

User profiles in Control Panel > System > Advanced SystemSettings > User Profiles:

The attributes that you can set in the Active Directory Users and Computers MMC snap-in are as follows:

  • Profile Path
  • Home Folder
  • Deny Logon to the RDSH server

Enable RCM in Windows Server

Important

Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.

Use either of the following registry values to enable the behavior of RCM in Windows Servers 2012 R2 and earlier versions:

  • Registry key 1:

    • Path: HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services
    • Name: fQueryUserConfigFromDC
    • Type: Reg_DWORD
    • Value: 1 (Decimal)

  • Registry key 2:

    • Path: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStations<Winstation Name>
    • Name: fQueryUserConfigFromDC
    • Type: Reg_DWORD
    • Value: 1 (Decimal)

Note

Microsoft Rdp Connection Manager

The default value for <Winstation Name> is RDP-tcp. However, this value can be renamed.

RCM behavior in Windows Server

At each user logon, RCM does the following things:

  • Query the Terminal Services registry key for the fQueryUserConfigFromDC value.
  • If the value is found and set to 1, contact the DC to get the user configuration information.
  • If the value is set to 0 or not present, query the Winstations key for the fQueryUserConfigFromDC value.

Are you missing good old terminal services manager (remote desktop services manager) from the Windows Server 2008 R2? For reason that is unknown to me as of today the Microsoft has decided to remove this mmc snapin that was a quick management tool, if you needed to kill the process on the specific server or check the users currently logged on the servers. As of today the Microsoft has not provided any official replacement for this handy tool.

That is pity because I have used the tool numerous times.

So I started researching if I can and to me seems that the tool from Windows 2008 R2 works on the Windows 2012, 2012 R2, 2016 and Windows 10 as well! :-) So everything you need to do is to copy file from here: tsadmin and do following steps:

  1. The zip consist 4 files, tsadmin.msc, wts.dll, tsadmin.dll and tsadmin.reg that I have created for this experiment to work.
  2. extract the files to c:WindowsSystem32
  3. Double click on the tsadmin.reg to add to the registry required information for the terminal services manager in order to load the MMC snapin
  4. Double click on the tsadmin.exe
  5. voila it works!
  6. The best is if you add more servers under mygroup, when you run it again it will just work and read the servers you have added before

So what you can do? I have tested to work with:

  • Windows server remote desktop services 2012
  • Windows server remote desktop services 2012 R2
  • Windows server remote desktop services 2016
  • Windows server remote desktop services 2019 build 17623 (at a time of the article the Windows 2019 RTM was not announced yet)

The functions working are:

  • disconnecting a session
  • sending message
  • resetting session
  • status of the session
  • logging of the session
  • ending a process on the processes tab (one of the simplest most important features of the tool)

Microsoft Remote Desktop Software For Windows 10

Let me know in the comments is it working as it should for you as well?

BTW if you need powerful full blown management tools you can take a look at SysKit Monitor.