Remote Desktop Manager is designed for managing all of your remote connections - from adding and editing to organizing or finding a remote connection quickly.
Download-->![Remote Remote](https://static.filehorse.com/screenshots-mac/file-transfer-and-networking/remote-desktop-manager-screenshot-03.png)
![Remote Desktop Manager 2019 1 4 0 3 Remote Desktop Manager 2019 1 4 0 3](https://static.filehorse.com/screenshots-mac/file-transfer-and-networking/remote-desktop-manager-screenshot-02.png)
Remote Desktop Manager Free 2020.2.20.0 is available to all software users as a free download for Windows 10 PCs but also without a hitch on Windows 7 and Windows 8. Compatibility with this remote connection software may vary, but will generally run fine under Microsoft Windows 10, Windows 8, Windows 8.1, Windows 7, Windows Vista and Windows XP. Virtualization and remote desktops are an important part of your infrastructure and work. And, we recommend that you use in-box remote desktop client (MSTSC) or universal Remote Desktop client instead of Remote Desktop Connection Manager (RDCMan). Remote Desktop Connection Manager 2.7.1406.0 is available to all software users as a free download for Windows 10 PCs but also without a hitch on Windows 7 and Windows 8. Compatibility with this remote connection software may vary, but will generally run fine under Microsoft Windows 10, Windows 8, Windows 8.1, Windows 7, Windows Vista. Lots off tools other than remote desktop are built into the app. Things like services, ping, port scan etc. Remote desktops open in tabs which makes it very easy to switch from server to server. Also the ability to store multiple passwords and assign them as needed is a real plus.' Chocolatey is software management automation for Windows that wraps installers, executables, zips, and scripts into compiled packages. Chocolatey integrates w/SCCM, Puppet, Chef, etc. Chocolatey is trusted by businesses to manage software deployments.
Remote Desktop Manager is designed for managing all of your remote connections - from adding and editing to organizing or finding a remote connection quickly.
It is fully compatible with Microsoft Remote Desktop, Terminal Services, VNC, LogMeIn, TeamViewer, Ftp, SSH, Telnet, and more. And now with the Enterprise Edition, you can share all your remote connection inside your company with SQL Server. Also, with the multiple data sources, each user can have their own personal remote connection.
Remote Desktop Manager integrates many tools and protocols like Microsoft Remote Desktop/Remote Assistance, pcAnywhere, Team Viewer, Radmin, VNC, Dameware, X Window, HP RGS, Logmein, and Citrix (ICA/HDX). You have the option to add even more solutions (via add-ons) to the configuration depending on your specific needs.
Download-->
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
Original KB number: 3200967
Remote Desktop Manager 2019 1 4 0 35
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 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. 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 by using the Local Users and Groups tool in Computer Management.
Remote Desktop Manager 2019 1 4 0 32
Docs expert 3 0. 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. This triggers an Active Directory query to check for RDP profile settings:
- Path:
HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services
andHKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStations<Winstation name>
- Name: fQueryUserConfigFromDC
- Type: Reg_DWORD
- Value: 1 (Decimal)
![Remote Remote](https://static.filehorse.com/screenshots-mac/file-transfer-and-networking/remote-desktop-manager-screenshot-03.png)
Then, restart the Remote Desktop Service. If the server doesn't have the Remote Desktop Service role installed, you must set up an additional registry key:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server
More information
The attributes that are on the Remote Desktop Services Profile tab of the users object properties in AD DS are not applied to the user when the user logs on to a Windows Server Remote Desktop Session Host (RDSH) server. Also, no warning is generated and no event is logged because the user's attributes are not enforced, and because everything is working as designed.
For example, if you are using the RDS attributes to specify a Remote Desktop roaming profile, users will not load that profile but will, instead, use a local profile. When this occurs, there are no error message or logged events. Therefore, the only way that you can know whether the user profile is not the RDS roaming profile is if you notice that the desktop environment is not the expected layout, or if you view the profile types in the system Control Panel applet.
Remote Desktop Services Profile tab in Active Directory Users and Computers:
Remote Desktop Manager 2019 1 4 0 3 X 4
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)
- Path:
- Registry key 2:
- Path:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStations<Winstation Name>
- Name: fQueryUserConfigFromDC
- Type: Reg_DWORD
- Value: 1 (Decimal)
- Path:
Note
The default value for <Winstation Name> is RDP-tcp. However, this value can be renamed.
![Remote Desktop Manager 2019 1 4 0 3 Remote Desktop Manager 2019 1 4 0 3](https://static.filehorse.com/screenshots-mac/file-transfer-and-networking/remote-desktop-manager-screenshot-02.png)
RCM behavior in Windows Server
At each user logon, RCM does the following things:
Remote Desktop Manager 2019 1 4 0 3 Download
- Query the Terminal Services registry key for the fQueryUserConfigFromDC value.
- If the value is found and it is 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.
- If the value is found and it is set to 1, contact the DC to get the user configuration information.