The RDCMAN is basically providing the same functionality as the Remote Desktops and allows you to create a consolidated console where you can publish information about the servers you need to remotely manage. Solution 1 – Use RDCMAN (Remote Desktop Connection manager)Īnother solution that a lot of people have been offering was to use the RDCman software. This might be acceptable for some time but at a certain moment, you will need to upgrade your infrastructure and are back to your initial problematic situation. One option (not really realistic) would be to update the console on a machine running Windows 2008 R2 or Windows 7. How do we solve this issue ? Possible Solutions Solution 0 – Update your console on Windows 2008 R2/Windows 7 If you try to add this snapin via the mmc.exe console, you will notice that this snapin console is not listed anymore
The problem shows up when the user is trying to update and modify this Remote Desktops console on a Windows 2012 R2 server. At this point, an operator or system administrator could open the Remote Desktops Console and work with it. The console has been created on the Windows 2008 R2 server and because of the move to Windows 2012 R2 infrastructure, the console has been copied over on Windows 2012 R2. For example, this customer had created a Remote Desktops Console listing multiple servers where an operator could connect remotely via rdp protocol However, some features or functionalities are missing. RDMS management console is basically providing and consolidating all these old mmc console into one location. In Windows 2012 R2, some of these consoles have been removed because the RDS 2012 R2 has been redesigned and most of the management is done through the RDMS console.
In Windows 2008 R2, indeed, we had a bunch of available mmc management console specifically designed to control and manage the Terminal services infrastructure.
0 kommentar(er)
