#REMOTE DESKTOP CONNECTION MANAGER SOFTWARE#
#REMOTE DESKTOP CONNECTION MANAGER WINDOWS 8.1#
#REMOTE DESKTOP CONNECTION MANAGER DOWNLOAD#
#REMOTE DESKTOP CONNECTION MANAGER WINDOWS#

There are now two sessions contained within our ‘Domain Controllers’ group. By default the display name field will match the server name field. In the second example below I have used the IP address of the second domain controller but amended the ‘Display name’ to show the short name. As my system has been setup correctly to append my lab domain name to short name addresses this will work just fine for me. In the first example I have only provided a short name for the ‘Server name’ attribute – either a fully qualified domain name (FQDN) or IP address is also a valid option. The next step is to add some sessions to this group – in this case I will add the two domain controllers from my home lab.

We will come back to the other menu options later in the article so for now don’t worry about them. As you can see below I have given the group a name of ‘Domain Controllers’ and also added a comment. We are presented with a new menu which gives us the chance to configure inheritable options for the remote desktop sessions which will be added to this group. Let’s add a new group and review some of the options provided to us. It is possible to add servers (remote desktop sessions) directly to this root object however I would recommend you create a logical folder structure to better organise and manage your connections. Now that we have our root level group created we can begin to create a folder structure to represent the various systems we manage on a daily basis. Assuming all is good though this is a great way of building out a connection profile that can be shared between admins and new starters. rdg file with other people – if you’re going to do this I’d suggest removing any credentials you may have saved (see below) or it may cause problems when they try to open and use it. I typically suggest saving this to your personal documents folder as it most cases in a business you are the only user to have access and it is likely backed up so you won’t lose it if your workstation dies on you. It’s important to consider where this will be stored as we can store authentication credentials within this object. The RDCMan group object will contain all of our settings, folder structures and remote desktop sessions.

#REMOTE DESKTOP CONNECTION MANAGER WINDOWS#

We can either use the typical Windows shortcut of Ctrl+N to create a new item or via the File menu. Let’s take a look at the interface following a standard installation –įollowing installation we have a basic screen with various menu options – we need to create a new ‘RDCMan Group’ which has a file extension of. Once RDCMan is installed we can start to configure it and take advantage of it’s various features.

#REMOTE DESKTOP CONNECTION MANAGER WINDOWS 8.1#

Support for Windows 8, Windows 8.1 / Windows Server 2012, Windows Server 2012 R2.

Support for credential encryption with certificates.

Virtual machine connect-to-console support.

Users using Windows XP or Windows Server 2003 will need to obtain version 6 or newer of the Remote Desktop Connection client software.įeatures introduced in version 2.7 are as follows –

Windows Server Tech Preview (Assume this means 2016).

To save you the trouble I will list provide the system requirements and details below – That being said the core features are pretty much all there so don’t let that put you off.

#REMOTE DESKTOP CONNECTION MANAGER DOWNLOAD#

I’m planning to be pretty in depth on this post so expect lots of screenshots and info.įirst off where do you get this fancy software? Well seeing as you asked so nicely I shall provide you with a link to the official download page!Ĭurrently we are on version 2.7 although to be fair it isn’t updated very often, the last release was on the 18th November 2014. It’s a great tool that makes life far easier and in this post I’ll cover some of the cool things you can do with it.

#REMOTE DESKTOP CONNECTION MANAGER SOFTWARE#

This is something I had done in the past till I came across the Remote Desktop Connection Manager software from Microsoft. I was speaking to somebody recently about how they connect to many remote Windows systems – in this instance they were opening up multiple MSTSC.exe windows and connecting that way.

Remote desktop connection manager