Solved Windows 10 Hyper-V Manager unable to connect to Server 2012 R2

[JaredBusch]

I have a client site running Server 2012 R2 + Hyper-V (mandated above me).

Anyway when it was first brought online, I had no problems connecting from a Windows 10 desktop to it via Hyper-V Manager.

Sometime in the last year or so it stopped working.

This is an all AD joined environment. So it was never a question about permissions as is common in a non-AD environment trying to manage Hyper-V

Because it was Server + Hyper-V I was a bit lazy about resolving it as I could always get to Hyper-V Manager from the server itself.

The error was always The Hyper-V Virtual Machine Management service must be running when of course it was.

I spent some time on Google this morning and found this link which resolved the problem.
https://social.technet.microsoft.com/Forums/en-US/1cc9115d-5fce-4a64-a90f-d3fdc008b861/windows-10-build-10240-managing-hyperv-on-2012-r2-datacenter-cannot-connect

On the Hyper-V server, in an elevated command prompt you run this.

MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof

You can read the details in the original thread.

[Obsolesce]

What caused it to break in the first place? I find it weird to have to fix it like that.

[JaredBusch]

The linked article had comments about a corrupt WMI data file

[dbeato]

@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?

[JaredBusch]

@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.