Devolutions ForumDevolutions Forum

RDM and Hyper-V on local machine

RDM and Hyper-V on local machine

avatar
rogerwilliams

Hi
I am struggling to configure an RDM session to connect to my Hyper-V machines. All the articles I've read regarding this seems horribly outdated, or does not contain sufficient details.

Here is my scenario:

  • I use Windows 10.
  • I have 2 Virtual Machines configured in Hyper-V Manager on my local laptop.


Questions:

  1. Do I need RDM installed on these VMs as well? If so, what steps do I need to take on the VM itself after installation on the VM, to enable access from RDM from my laptop outside of Hyper-V?
  2. Do I need to start the local virtual machines first before I can access them via RDM?
  3. Do I need to proceed to logon to the VM first before I can access them via RDM? This means that this would result in a constantly open VM window plus the RDM connection window, which I was hoping to avoid.
  4. Within RDM on the laptop, what are the exact steps I should take to configure a session connection to these local VMs? Example: session type, which tabs, what fields to populate on the various tabs, etc.


Thanks
Roger

All Comments (2)

avatar
Etienne Lord

Hello,

Thank you for contacting us, I will have to verify your different questions with the engineering department, keep you updated on that!

Best Regards,

Etienne Lord

avatar
Marc-André Moreau

Hi,

1) RDM does not need to be installed on the Hyper-V host, or inside the Hyper-V guests
2) You need to ensure the VMs are already in the running state before connecting to them from RDM
3) You do not need to login to the VM before connecting to them from RDM, but you will still need to manually login to the VM once connected
4) Within an RDP connection entry, you can choose to connect using the VM Name or VM Id - selecting either one will make the Hyper-V property tab appear.

Here are a few important things:

Hyper-V RDP authentication is always with the Hyper-V host, there is no login integration for the VM guest. In other words, you need to login with a user with sufficient rights on the Hyper-V host but all you'll get inside the VM is Winlogon for a second login. You can use the RDM "type clipboard contents" feature to "paste" a password since Winlogon does not support the clipboard.

We don't really have an Hyper-V manager replacement, only a vmconnect.exe replacement, which is why you need to start the VMs by yourself. We connect to the VMs but we don't have advanced VM management. Also, make sure that your current user is a member of the Hyper-V administrators group, otherwise you may need to launch RDM elevated for things like connecting using the VM Name.

Hyper-V only accepts connection requests using the VM ID, and mapping the name to a VM ID requires access to Hyper-V. If you configure the connection entry with the VM ID you can bypass the elevation requirement (or Hyper-V Administrators group membership).

I hope this helps

Marc-André Moreau