Remote Connection Manager 2.7



  1. Remote Desktop Connection Manager 2.7 Free Download
  2. Remote Desktop Connection Manager 2.7 Portable

Trusted Windows (PC) download Remote Desktop Connection Manager 2.7.15120. Virus-free and 100% clean download. Get Remote Desktop Connection Manager alternative downloads. Using MS Remote Desktop Manager 2.7 on Windows 10. It has been a great tool to keep all my RDC connections. I just switched to a new PC and copied over my RDG file to the new PC. Now getting error: 'Object reference not set to an instance of an object when trying to save'. This occurs when I am trying to save after changing settings for a.

Last week Microsoft released Remote Desktop Connection Manager version 2.7 (aka RDCMan). It has some really cool features and supports Windows 8.1 and Windows Server 2012 R2. This tool is essential if you run a lot of virtual machines. One of the new features allows the ability to connect directly to virtual machines (called virtual machine connect-to-console support). Configuring a connection for this new feature is rather easy once you have the ID of the virtual machine. The following PowerShell command should do the trick:

Once you have this information, enter it on the Server Settings tab like in the following screen shot:

Connection

Download canon pixma mp280 driver for mac. The Server name field is the name or IP address of the Hyper-V host and not the VM.

Once you have this setup, you should be all set…that is unless you get the following error like I did (BTW – I am running Windows 8.1 Enterprise x64 on my laptop as my Hyper-V host):

Remote Desktop Connection Manager 2.7 Free Download

Disconnected from VMNAME (192.168.1.243)
[Unknown disconnection reason 3848]

The reason for the error appears to be that the Credential Security Service Provider (CredSSP) policy on the Hyper-V host is not enabled to authenticate user credentials from a remote location. Setting the following registry keys fixed part of the problem for me.

One other thing that I had to do in order to get this to work was to add my account into the local Hyper-V Administrators group on my Hyper-V host (even though my account was already a local administrator). Now when you connect to a VM and you are prompted for credentials, use your credentials for the Hyper-V host for the initial prompt. These credentials can also be saved on the RDCMan Server Properties under the Logon Credentials tab. Once connected, that will bring you to the logon screen of the VM where the credentials for the VM are entered.

More information about the CredSSP policy issue, as well as alternate configurations (i.e. GPO), can be found in the following knowledge base article:

Remote Desktop Connection Manager 2.7 Portable

Originally posted on https://miketerrill.net/