@scottalanmiller I believe @dave247

@dbeato said in Windows 10 Hyper-V Manager unable to connect to Server 2012 R2:

@jaredbusch said in Windows 10 Hyper-V Manager unable to connect to Server 2012 R2:

, in an elevated command prompt you run this.
MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.

Interesting, that was the issue you were having last week right?

Nope. Different client.

That location is a firewall issue.

@darek-hamann said in Configuring Windows Server 2016 Core. Part 2: Hyper-V role installation:

@dashrender

This is actually a great article! It simplifies the procedure of installing a Hyper-V role from a GUI free Windows 2016 Core setup.

That's nice, but again - WHY. This is not the way you should NORMALLY install Hyper-V because now you have a license tied to the hardware. I get that there are reasons, but I'm asking what they are.

If it is a restart of the Hyper-V host, then check the services once it fails to respond like that.

That doesn't really surprise me that it's a bandwidth hog like that...