Friday, 12 October 2012

SCVMM 2012 SP1 - Missing properties and unable to refresh VM

Giddy as a kid in a sweet shop I migrated my testlab cluster to Server 2012, migrated my VM's across and installed System Center 2012 Virtual Machine Manager SP1 to manage it.

Straight away I ran into some slightly strange issues.

  1. Majority of the Auto Discovered VM's refused to see hardware configuration properties such as:
    Virtual Hard Disks and Controllers
    Virtual Network Cards
  2. Majority of the Auto Discovered VM's left hardware configuration properties at defaults, such as:
    Processor Count and Memory Amount
    High Availability Status
  3. Every time I tried to refresh a VM I would get the error:
    Error (2923)

    A malformed response was received while trying to contact the VMM agent on hyperv01.domain.local.
    Unspecified error (0x80004005)

    Recommended Action
    1) Ensure the VMM agent is installed and that the SCVMMAgent service is running.
    2) If the SCVMMAgent service is running, restart the service, and then verify that WS-Management is installed correctly and that the WinRM service is running.
    3) Check the manufacturers' Web sites to ensure that you have the latest drivers for your network adapters and other devices.
Looking on the Microsoft Connect site I found that someone called egilsk was having the same issues.

Thankfully, last Friday (05/10/12) Mark at Microsoft posted the following suggestion to try:

On the Hyper-V hosts run the following PowerShell commands

Import-Module Hyper-V

Get-WmiObject –Namespace “root\virtualization\v2” Msvm_PlannedComputerSystem | foreach{Get-VM –Id $_.Name} | Remove-VM –Force

Once this has been run on your hosts, refreshing the VM's should work successfully and all of the missing/default hardware config should be updated and displayed.

It looks like this is to do with the hosts having the VM stuck in a temporary state, even if brought across as a planned import or migration.

The problem is now at least known about and should be fixed/handled in the next release of the Service Pack.

No comments:

Post a Comment