ecarbone

Sorry, should have mentioned - this is a Microsoft Hyper-V session in RDM, not a Microsoft Remote Desktop session.

The reason I added it as a Hyper-V session is because it looks like with just this one icon you get the best of both worlds - a complete list of every VM on that host (and the ability to connect to any of them) as well as the ability to remote directly into the host.

When you edit the properties of the Hyper-V session, there's not nearly as many options. So, no option to control drive mapping, etc.

Here's a screen shot ...

https://www.screencast.com/t/OULXpPTC5b2

5.1.3.0 64-bit.

When I click Check for Updates it says I have the latest version.

When I connect to my Hyper-V Host, I see all of my local drives inside of the host. In Microsoft Remote Desktop, you can uncheck Drives under the Local Resources tab. How do I disable it in Remote Desktop Manager?

The Add New Entry screen looks different for me, and I do not see a Synchronizer option.

https://www.screencast.com/t/ScdharTd2

Hyper-V Synchronizer seems promising but I don't see it when I launch RDM.

I've never used RDCMan from Microsoft and I forgot ActiveX was still a thing ;-) I enabled the "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)" option and that resolved the issue for me. Thanks for the quick reply.

I added a shortcut for a Hyper-V Console session.

When I try to connect I get an error "The connection cannot proceed because authentication is not enabled and the remote computer requires authentication be enabled to connect".

But when I click OK it connects anyway.

On that server in System Properties > Remote > Remote Desktop the option "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)" is UNCHECKED.

Host is running Windows Server 2016 Standard

If I check that option under Remote Desktop and then try to connect again, it works with no error.

I'll keep that option checked (I had unchecked it due to a remote desktop issue resulting from a windows update a few months ago), but I am just curious why RDM gives an error telling me 'the remote computer requires authentication' when the option is actually unchecked on the server.

Screen shots:

https://www.screencast.com/t/5EWObl7hX

https://www.screencast.com/t/eiLmqlEU4

Currently evaluating Remote Desktop Manager - great program!

I have a few questions:

1. I've created some folder structures and inside of folders, I have added some remote sessions. I notice when setting up a folder, there are fields for me to enter credentials, OS, Host, IP, etc. Seems strange that the program would be asking me for this information when all I am doing is creating a folder. What's the purpose of adding this type of info to a folder? I assume there's a reason and I am just missing the point. (Inside of the folder, I created a Microsoft Hyper-V Console. Here in the console, it makes sense that this is where I would enter my credentials. And so I do. And it works. When I open that session, RDM logs me in and I can see the list of VMs on that server.)

2. I'm used to launching Microsoft Hyper-V Manager where it remembers my servers and automatically displays the list of VMs. But if I wanted to use RDM as a replacement for Hyper-V Manager, it seems there are more steps. Is there a way to have RDM automatically connect and display the list of VMs on each host? It looks like each time I launch RDM, I have to click on each Hyper-V server, one by one, and then click the Open Session button and then wait or the list to be populated.

3. That being said - let's say I did launch RDM and then connect to every Hyper-V host. The end result is I have a quick way to manage all the VMs on each host, and in this state it seems like a good replacement for Hyper-V Manager. But... does it eat up resources by having all of the servers in the 'Connected' state all day long?

4. If I add a Hyper-V Console to RDM, and then connect to it, I see my list of VMs. But from within that list, double-clicking on a VM does not remote into it like Hyper-V Manager does. I'd have to right-click on the VM and select Connect (or click on the button in the ribbon although in my opinion the ribbon is too intrusive and takes up too much room, so I opt to leave it hidden). Once I have connected, I have to ctrl-alt-del and enter the password. Seems tedious.

I found that instead of adding a Hyper-V console to RDM, I add a 'Microsoft Remote Desktop' session.

The benefits to this method are (1) now I can double-click on it to connect to that VM (just like I am used to with Hyper-V Manager) and (2) it can remember my password and automatically log me in and (3) I can connect to multiple VMs inside of the nice tabbed interface. The down-side to this method is (as far as I can see) I have to manually, one by one, add every single VM to RDM and save it. One. At. A. Time. I have over 100 VMs.

Isn't there a way to have all of this in one easy session? In other words (1) Add JUST the Hyper-V Server to RDM (not every single VM one at a time), then (2) have it auto connect to each server (every time I launch RDM) and automatically list all of the VMs, then (3) allow me to double-click on any VM within the Hyper-V Server and have it automatically connect AND log me in, using the tabbed interface, without prompting me for a password?

Excellent, that worked!

Any way to get it to remember the password? RealVNC launches, but I have to enter the password every time it connects.

(Whereas if I just launched RealVNC and double-clicked on my shortcut, it would connect using the saved password)

I have an old Windows 7 machine that (for whatever reason) I can only connect to using RealVNC. If I try to connect to that same computer using UltraVNC, I get an error 'No supported authentication methods'. If I connect using RealVNC, it connects just fine.

With that in mind ... I was trying to add this connection to Remote Desktop Manager. When adding a VNC session, I can only choose between 'Default' or 'UltraVNC'. I assume that if I select 'Default' it will use my default VNC app (which is RealVNC). Selecting 'Default' from the drop-down changes the icon to the RealVNC icon. However when I try to connect using Remote Desktop Manager I get an error 'Unable to connect to host xxx!'. If I try switching the drop-down to UltraVNC, I get 'No supported authentication methods'.

I don't really care why I am unable to connect using UltraVNC. However, I do need RealVNC to work through Remote Desktop Manager. It works on its own, but when I initiate it through Remote Desktop Manager I get the 'Unable to connect to host' error. Any idea why?