共用方式為

Update Rollup 2 for System Center 2012 SP1

  • 發行項

imageThis blog focuses on VMM and Orchestrator, and for VMM alone there are 20 fixes in this update. Many of these corrections relate to networking. This update has helped a number of customers I have worked with resolve their issues entirely. Even in a controlled classroom environment (I’m out delivering training this week. Go OKC!) the update has made a strong positive impact. As for Orchestrator, there are a few fixes as well, both of which stemmed from customer cases I worked involving Oracle results and SNMP Traps.

 

This is one update that should be installed immediately, or as soon as your outage window allows. There is one caveat: ‘In order to install Update Rollup 2 package for System Center 2012 SP1- Virtual Machine Manager, you will need to uninstall Update Rollup 1 for System Center SP1 - Virtual Machine Manager package from your system. ’ See this blog post for a great deal of information on the subject. Also, if you need to uninstall SC VMM for some unrelated reason, you will need to remove this update first to do so.

Grab the update here. Description of Update Rollup 2 for System Center 2012 Service Pack 1

A list of fixes in the update…

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.

 

 

 

 

 

  jonjor

Comments

  • Anonymous
    January 01, 2003
    thank you