Wednesday, January 16, 2013

Hyper-V 2012 known issues

Here are 2 known issues as advised by the Microsoft Product Group. I have not encountered it yet, but hope it helps someone that has...

  • Virtual machine enters a paused state or a CSV volume goes offline when you try to create a backup of he virtual machine on a Windows Server 2012-based failover cluster. A hotfix is available for this condition at
  • Managing Hyper-V hosts using Virtual Machine Manager fails after installing WMF 3.0 (KB 2795043). The hotfix for this specific condition is documented in KB 2781512, available at the following location:

System Center Universe APAC 2013!

The second installment of System Center Universe Asia Pacific is confirmed for January 31, 2013! SCU will be a global event starting from APAC, hosted and broadcasted LIVE from Singapore. After which, sessions will start in Irving, Texas, USA!

Join us in Singapore, or watch it LIVE.

I will be speaking on the topic of "Service Pack 1 is HERE!, What's in it for me??"

Check out details at to attend or listen in on the live broadcast.

Also check out for the US event! sessions will also be broadcasted LIVE, so you can join in.

Hope to see you there!

SCCM Service Pack 1 Client Fails to Install - Error 0x800b0101

I recently encountered a failure in installing an agent when I had already upgraded my SCCM 2012 server with Service Pack 1. I had no problems installing agents before this. Looking at the CCMSETUP.LOG file using the Trace utility, I noticed this line being highlighted:

Couldn't verify 'C:\WINDOWS\ccmsetup\MicrosoftPolicyPlatformSetup.msi' authenticode signature. Return code 0x800b0101

Searching on the net, I found that this was a known issue and a patch available at

After applying the patch, the SCCM Agent deployment was successful.

Failover Cluter Manager FAILS after applying kb2750149

This is a known issue and has been verified by the Microsoft Product Group.

If you applied KB 2750149 in a Windows Server 2012 Clustered server, you may find that Failover Cluster Manager will FAIL to load and no longer usable. The error that you will see is..

“A weak event was created and it lives on the wrong object, there is a very high chance that this will fail, please review and make changes on your code to prevent this issue"

At this point of time, the only resolution is as follows:
  • Uninstall the KB patch (best method)
  • Manage the cluster with a remote Failover Cluster Manager console or SCVMM (some customers have reported that this patch also affects management using SCVMM)
  • Manage using Powershell