We had some issues with VMM after RU6 and RU7 update. Hyper-V host,Cluster changes are not getting replicated to VMM.
Symptom
1. After you VM shutdown the VM(Using RDP), VMM console shows guest VMs are still running until you manually refresh the guest VM to change the state
2. Guest Vms status are not getting refreshed immediately on VMM server
3. We have live migrated the Guest VMs using failover cluster console and found the console changes are not getting updated in VMM. We tried to refresh the guest VM and got the failure message
Cause- Host machines in the cluster had legacy refresh mode enabled.
After the RU6 and RU7 updates, all the hosts state have changed to legacy from eventbased and Microsoft recommend us to keep eventbased for VMM managed hosts
Refer the below link for eventbased and legacy mode details
http://blogs.technet.com/b/chengw/archive/2012/09/17/update-on-vmm-refreshers-what-has-changed-and-what-this-means-to-you.aspx
Solution
Login to VMM Server and run the below powershell(step1) to get the host details. If you see legacy, then change the refresh mode to Eventbased using step2
Step 1.
Get-SCVMHost | Sort-Object Computername | ForEach-Object { "{0}, {1}, {2}" -f $_.Name, $_.Host
Cluster.Name, $_.GetRefresherMode() }
Step 2.
$vmhost=get-scvmhost –computername <Computername>
$vmhost.ResetRefresherMode()
Step 3.
Refresh all the VM from VMM console - Right click on host and refresh all VM
Step 4.
Run the step 1 command to see the status
Note: You have to run the commands to each host(step2)