Review for Packt ‘Building and Managing a Virtual Environment with Hyper-V Server 2012 R2’ by Eric Siron

I recently worked my way through the video series ‘Building and Managing a Virtual Environment with Hyper-V Server 2012 R2’.

The Videos consist of short modules covering the relevant Hyper-V and Cluster topics. Each example operation is demoed using both GUI and powershell. The total time of the material is just under 3.5 hours, this results in a sufficient amount of time to get a reasonably good overview of each feature required to think about the design, and maintenance of a Hyper-V Failover cluster.

I generally much prefer books and articles than videos when I am checking up on things, videos are much better suited for people wanting an overview or introduction into subjects.

The video is made by author Eric Siron. Eric has contributed a great deal to the Hyper-V community and is known for his various publications including papers on the Altaro Hyper-V hub site  and his book ‘Microsoft Hyper-V Cluster Design‘.


Eric’s new video ‘Building and Managing a Virtual Environment with Hyper-V Server 2012 R2’ is available from Packt Publishing.


VMM 2012 R2 Error 12711 (VMM cannot complete WMI operation on the server) Removing an Orphaned Clustered Resource (Failover Cluster 2012 R2)

Sometimes admins attempt to repair VMs, not knowing about the relationship between VMM/Failover-Clustering/Hyper-v they fix up a VM to a working state, leaving empty orphaned cluster resources behind, and also causing VMM to report error 12711.

To fix these resources we need to get into powershell and connect to the cluster.

Start with a “Get-ClusterResource” and see if you can see it, try remove it using the “Remove-ClusterResouce” command first, if this fails (as it sometimes does if its an empty VM resource) then we can try removing its group with contents

do a “Get-ClusterGroup” and identify the name, now try “Get-ClusterGroup nameofGroup | Remove-ClusterGroup”

still not working? -group is not empty error? thats fine try “Get-ClusterGroup nameofGroup | Remove-ClusterGroup -RemoveResouces”

Disk 2 VHD – P2V Tool for Hyper-V

Disk 2 Vhd 2.0 is now out! it supports direct conversion to vhdx. head over to the below link for more information:

SCVMM 2012 R2 – Error 20506 / 20552 / 2606

Had an interesting issue today, All hosts spread over two clusters were in a state of ‘not responding’ with no clear explanation why.

It looked as though the issue began at 2am, a time when nobody would have been working on the VMM console.

Initial diagnosis showed that the network was up, The Failover Cluster was working just fine, but VMM had lost WinRM connectivity to the hosts.

The usual error 20506 appeared in the host status window indicating that WinRM “could not complete the Windows Remote Management request on computer xxx”

Furthermore each time the Refresh Host Cluster job would fail it would show errors

2606 – unable to perform the job because on or more of the selected objects are locked by another job

20552 – VMM does not have appropriate permissions to access the resource on the xxx server

I spent a fail amount of time looking into the WinRM issue, everything was fine and nothing had changed. WinRM tests showed that the VMM server was able to communicate with the hosts.

I looked for locked jobs or running jobs, even checking the SQL server using the query

SELECT * FROM [VirtualManagerDB].[dbo].[tbl_VMM_Lock] where TaskID=’Task_GUID’ (See )

but that showed no jobs were active at all.


The thing that resolved it, was running another job (a non cluster related job) in my case i changed a run-as account. As soon as this went through I was able to refresh the cluster just fine.

I cant completely explain this one, my guess is that a phantom job had gotten stuck somewhere. Thought i would share the results.


Live Migrations Fail between SCVMM 2012 SP1 hosts

While performing some cleanups for a client I noticed a problem where certain live migrations were failing.

I knew I had been performing updates on various hosts to bring them in alignment. Upon closer inspection I could see that the Virtualization Software Version was changing on hosts that had been updated:

Virtualization Software Version Mismatch Clean zoom


In the above snip you can see the host in Maintenance mode has a different version of the virtualization software. The version field is talking about the Hyper-V version, rather than the VMM agent version.

As usual, when something fails in SCVMM often the next step is to try it in failover cluster manager, results below:


Unfortunately because I had been updating the hosts while they had running VMs on them (and then placing them into maintenance mode once they were ready to reboot) I was left with one host that would not allow live migrations.

The solution?

I had to use Quick Migration to move the VM’s, while this is not technically live, it was quick enough to get the job done.

Lessons learned? Place servers into maintenance mode before you start patching! and keep all your hosts at the same level.


Also it is worth pointing out that there have been some particularly damaging patches released by MS recently, rather than explain it myself I will point you to Aidan Finn’s blog where he talks about the problematic patches.