2013
01.08

Microsoft has published a KB article (KB2795043) that explains the following scenarios:

On System Center Virtual Machine Manager, you may experience one of the following symptoms:

  • A Windows Server 2008 R2 SP1 Hyper-V host has a status of Needs Attention in the VMM Console.
  • or

  • Adding a Hyper-V host or cluster fails.

The fix is … to uninstall the WMF 3.0 update (KB2506143).  There’s a bit more to it than that. You also need to reboot the host and then run:

winrm qc

… and then do another reboot of the host.

I know; it’s far from an ideal situation.  But there’s the workaround for you.

Copyright Warning

This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.

Related posts:

  1. KB2710870–No DHCPv4 Address After Restarting Hyper-V VM with Vista, Win7, W2008 or W2008 R2
  2. Using VMM 2012 SP1 Baselines & Compliance To Orchestrate Patching Of Hyper-V Hosts
  3. WS2012 Hyper-V – What You Can Install On The Management OS

1 comment so far

Add Your Comment
  1. Thanks Aidan, this issue has been plaguing us for the last month or so. For us the problem wasn’t that the hosts had “needs attention status”, they all had OK status, but we couldn’t for example connect a vNIC to a vSwitch, this would always fail. Other symptom was that we couldn’t manage vSwitches from VMM. Following the steps in the mentioned KB fixed the problem for us.

Get Adobe Flash playerPlugin by wpburn.com wordpress themes