Here’s a quick summary of the issues fixes with the February rollup release.
Performance and Resource Optimization (PRO) Tip alerts are not displayed in the SCVMM Admin Console if the alert resolution state is set to a value other than 0 in System Center Operations Manager 2007.
If a network adapter for a Hyper-V host uses teaming software, Virtual Machine Manager (VMM) may incorrectly bind the Virtual Switch to the host network adapter.
A Virtual-to-Virtual (V2V) migration to a Cluster Shared Volume (CSV) volume fails if the cluster node that owns the volume has insufficient disk space on the system volume. Additionally, you receive an error message that resembles the following:
Error 2606 - Unable to perform the job because one or more of the selected objects are locked by another job.
A Physical-to-Virtual (P2V) migration from a computer that is running Windows Server 2003 fails. Additionally, you receive an error message that resembles the following:
Error 416 - Agent installation timed out while waiting on service VMMAgentInstaller on servername.domain.com.
The network migration of a highly available virtual machine to a different cluster fails. Additionally, you receive an error message that resembles the following:
Error (12711) - VMM cannot complete the WMI operation on server servername.domain.com because of error: [MSCluster_ResourceGroup.Name="4168e895-2831-32cf-b4d8-352ac13e28c9"] The cluster group could not be found.
(The cluster group could not be found (0x1395))
To automate your installation, use msiexec /update PackageName.msp BOOTSTRAPPED=1
For more information: KB 2492980