Share via

Changes to Remote Management using Hyper-V Manager

  • Article

In Windows 10 and Windows Server 2016 we have made some significant changes to the way Hyper-V Manager connects to a remote system.  From an end-user perspective there are a couple of new things that we now support:

  • You can now provide alternate credentials when connecting to a remote computer
  • You can now connect to a remote computer using just the IP address

From an systems architecture point of view – this is the result of two big changes under the covers:

  • The Hyper-V UI and Hyper-V PowerShell commandlets now share a common back-end infrastructure (this is a big win for quality and consistency of experience)
  • Both of them now use WinRM instead of WMI directly

However, this does mean that the process for getting remote management configured has changed in a number of subtle ways.  If you are struggling to get Hyper-V Manager working remotely on Windows 10 / Windows Server 2016 – there are two things to know:

  1. We have documentation up here: https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/user_guide/remote_host_management
  2. If you are used to configuring PowerShell Remoting – we now have exactly the same requirements.  If PowerShell Remoting with CredSSP works – then Hyper-V Manager will work.  (Here is a handy guide on this: https://blogs.technet.com/b/heyscriptingguy/archive/2012/11/14/enable-powershell-quot-second-hop-quot-functionality-with-credssp.aspx)

Cheers,
Ben

Comments

  • Anonymous
    February 05, 2016
    Is there a simple way (i.e. a built-in cmdlet one-liner) to obtain the CPU %, memory utilization of a remote Hyper-V server?
  • Anonymous
    July 14, 2016
    Guys, the work you have delivered is just awful! - No user experience at all. I am experimenting since three evenings with partial success. Do yourself a favour and install one of your competitors product and see what happens. - Install, connect via browser, configure it, done! In less than 10 minutes . . . .
  • Anonymous
    October 28, 2016
    Thanks for the efforts here! About time we got alternate credential support, but, while this works, using an IP address to connect does not.
  • Anonymous
    November 24, 2016
    The handy guide link goes to a general page that did not seem to have anything relevant.I've been trying to manage HV-2016 for over 2 weeks now.Rich W.
  • Anonymous
    August 13, 2017
    I had successfully been remote managing a standalone install of Hyper-V 2016 from a Windows 10 PC. All of a sudden It just stopped working. I now get an HTTP 403 error. When I try to connect to the 2016 host. I've been posting about this in every forum I could think of. Still no one has been able to help.