Connect to virtual machine on Hyper-V¶
When set up properly, you can use mRemoteNG to connect to virtual machines running on Hyper-V. This how to provides you with all the information you need to get things running.
To be able to connect to the virtual machine we need its’ id. You can find it by executing the following powershell command on the Hyper-V server:
Create a new connection, set the protocol to RDP and set the “Use VM ID” property to true. Enter the id in the new property field that just appeared in the connection section and set the port to 2179.
Enter the id of the virtual machine you found out earlier and you are able to connect to the virtual machine.
For the scenario above to work there is some configuration that may be necessary for you to set up, depending on your environment.
You must be a member of the Administrators and Hyper-V Administrators groups on the Hyper-V Server to be able to remotely connect to any virtual machine running on the host via VMRDP. If this is not the case your user has to be granted access to remotely access the machine. The following Powershell command achieves this:
Port 2179 must be open on Hyper-V server and on the machine you are connecting from. Use the following command to open the ports on the firewall if needed:
In case you are facing “Unknown disconnection reason 3848” error when connecting, you need to configure a number of registry settings on your client and the Hyper-V Server to make the connection work. This problem occurs because of the CredSSP (Credential Security Service Provider) policy on the client and/or Hyper-V Server not allowing to authentication of remote users by default.
See Microsoft support file 954357 for more information on this topic.
For more information on RDP error codes see this Microsoft article.
Start the PowerShell console with administrative privileges and run the following commands: