System Center 2012 SP1 Virtual Machine Manager Update Rollup 2

System Center 2012 SP1 Virtual Machine Manager Update Rollup 2

System Center 2012 SP1 Virtual Machine Manager Update Rollup 2System Center 2012 SP1 Update Rollup 2 for VMM is now available for download. The previous Update Rollup 2 released for System Center 2012 SP1 did not include fixes for VMM (UR2 for System Center 2012 SP1). The rollup (UR2) for VMM 2012 SP1 includes around 20 issues with VMM.

The downloads are available through Windows update and if you’d like to manually download:

VMM Server (KB2826405): VMM Server update package

VMM Administration Console (KB2826392): VMM Administration Console update package

Description of Update Rollup 2 for System Center 2012 Service Pack 1

You should be careful with this update; If you have previously installed UR1, you need to uninstall this update first.

  1. If you install UR2 for VMM manually by downloading files from update catalog and install it without uninstalling UR1, you will need to uninstall UR2, then UR1 via Control panel, add/remove programs and features
  2. If you have installed UR1 via Windows Updates, you will NOT be offered with this update till you uninstall the UR1. 

Basic Steps:

  1. Close all VMM consoles, and make sure you don’t have any job running on VMM server.
  2. Uninstall UR1 from Administration Consoles and VMM Server

    Control Panel:
    Update Rollup 1 

        or from elevated CMD prompt:

  3. VMM Console x64
    msiexec /I {CDFB453F-5FA4-4884-B282-F46BDFC06051} MSIPATCHREMOVE={32A2C205-610D-4C45-B5C0-ADC606346D2E} BOOTSTRAPPED=1
    VMM Console x32
    msiexec /I {0DAD2A89-CF75-4448-97AF-72C7CC18B8A5} MSIPATCHREMOVE={32A2C205-610D-4C45-B5C0-ADC606346D2E} BOOTSTRAPPED=1

    VMM Server UR1
    msiexec /I {59518B15-FC64-4CF9-A4D1-0EE1B4A63088} MSIPATCHREMOVE={4EA74929-330D-49EC-B8EC-8A3219869A62} BOOTSTRAPPED=1
  4. Install UR2:

        Once done, the version will be 3.1.6020.0 on the VMM Console

  5. You will need to update VMM agents on the hosts.

        Open VMM console, right click on hosts that have status “Needs Attention” and click on “Update Agents”.

        Once done, the version of host agents will be 3.1.6020.0 (Host Properties/General/VMM Agent)

List of issues fixed:

Description of Update Rollup 2 for System Center 2012 Service Pack 1

Virtual Machine Manager Server (KB2826405) and Administration Console (KB2826392)
Issue 1

The SUSE Linux Enterprise Server 11 operating system is missing from the Linux OS list.

Issue 2

A virtual machine cannot start after migration from Windows 7 to Windows 8 when the DiscardSavedState method is used.

Issue 3

A connection to the VMware virtual machine remote console session cannot be established.

Issue 4

Externally published VMNDs are filtered incorrectly.

Issue 5

When you remove a virtual switch extension property or edit a virtual switch extension manager connection string, a user-interface generated script also removes the HostGroups that are associated with VSEM.

Issue 6

UPPSet is not set on a physical network adapter when you add the network adapter to a team and when the network adapter is the first in the list of network adapters.

Issue 7

The default gateway is missing on a host virtual network adapter after you add a second physical network adapter to the logical switch.

Issue 8

Static IP pool that has the first address in a subnet fails for external network type.

Issue 9

VMM crashes during host refresher when VMM is unable to create a CimSession with the remote host.

Issue 10

Standard (legacy) virtual switch creation on Windows 8 hosts with management virtual network adapter does not preserve the IP properties of the physical network adapter.

Issue 11

The administration user interface crashes with a NullReferenceException error when you click Remediate on a host instead of a virtual network adapter.

Issue 12

The Virtual Machine Manager user interface displays a network adapter in a "Not Connected" state.

Issue 13

The Virtual Machine Manager stops responding with high CPU usage for five to ten minutes when you configure a VMND that has 2,000 network segments.

Issue 14

The host virtual network adapter property for a management adapter does not show port classification.

Issue 15

Live Migration fails at 26 percent when the network adapter is attached to an isolated virtual machine network.

Issue 16

The Virtual Machine Manager Service crashes when a virtual machine that does not have a port profile is migrated to a cluster by using a logical switch that has a default port profile set.

Issue 17

Running Dynamic Optimizer on a cluster with incompatible host CPUs causes a Virtual Machine Manager Service crash.

Issue 18

The Host refresher crashes for any host that has the RemoteFX role enabled.

Issue 19

The minimum memory for dynamic memory greater than 32GB is a security risk.

Issue 20

The status of the network adapter is displayed as Not Connected in Virtual Machine Manager.

Bulent Tolu
Latest posts by Bulent Tolu (see all)
Translate »