Windows – Hyper-V Server R2 – Disk management MMC returns RPC Server is unavailable

To connect using Hyper-V manager from a workgroup machine to an Hyper-v domain member server you also need allow anonymous DCOM remote access.

There is a tool from Microsoft that configues automatically all the necessary things for you: Hyper-V Remote Management Configuration Utility.

If this not work i would recommend you to check the Windows Credential Manager of the client machine looking for bad entries. If you are not sure, delete all of them.

And finally, off course could be a really RPC error, the RPC error could be failing in your server. For be sure that it is not the issue connect to the server using MMC with other Snap-in as example Local Users and Groups.

Looks to be an issue with HyperV snapin crashing when running on a second monitor

You aren't going to believe this. We figured out what it was finally and it was fairly complicated :)

We found a bug with the Hyper-V MMC snap in that is very repeatable. With Win2k8R2, hook up a machine to an external monitor (I was doing this on a laptop). Then, move the MMC (server manager in this case) the external monitor. Try to right-click on any VM in Hyper-V and it will crash. As soon as you move it back to the main monitor it works fine again.

Go figure!

I can confirm these results on my system, which has 2 GPUs with 4 monitors total (See below). If i use HyperV manager on the primary display or lower half of monitors 3 and 4 then everything works, but as soon as I move it above the vertical height of the primary display and try to right click it will crash. I have been working with Microsoft Support to resolve the issue (SR number 112110960192323 ) and will follow up if a hotfix or workaround is found.