SCVMM 2008 R2 February Rollup Released!

  • Article

Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: February 8, 2011

https://support.microsoft.com/kb/2492980

SCVMM Rollups are cumulative, so install this latest update whether or not you have installed prior rollups. The number of issues resolved makes each of these updates vital to maintaining a healthy SCVMM environment.

By stopping the ‘Virtual Machine Manager’ and ‘Virtual Machine Manager Agent’ services on the SCVMM server prior to install, a server restart should not be required. Although this update is available on Windows Update, it is strongly recommended that a manual download and install be performed. This is to guarantee installation in the event that your corporate WSUS server does not provide the update, or only the most recommended updates are installed.

Keep in mind that to perform a manual install you must open an elevated command prompt and type the command below, substituting the correct version of package name. This is explained in the associated article.

msiexec /update PackageName.msp BOOTSTRAPPED=1

 

 

List of issues that are resolved

Issue 1

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.

Issue 2

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. 

Issue 3

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.

Issue 4

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.

Notes

  • servername is a placeholder for the name of a server.
  • domain.com is a placeholder for the name of the domain that the server joins.
Issue 5

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))

Notes

  • servername is a placeholder for the name of a server.
  • domain.com is a placeholder for the name of the domain that the server joins.

 

This hotfix rollup package includes also the hotfixes that are documented in the following SCVMM 2008 R2 hotfix rollup packages:

2308590 (https://support.microsoft.com/kb/2308590/ ) Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: September 14, 2010

982522 (https://support.microsoft.com/kb/982522/ ) Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: June 8, 2010

978560 (https://support.microsoft.com/kb/978560/ ) Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: February 9, 2010

976244 (https://support.microsoft.com/kb/976244/ ) Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: November 10, 2009

 

 

  Are you up to date? Use VMMUpdate to find out!

  jonjor