How to install System Center 2012 SP1 Update Rollup 2 for VMM

System Center Logo

Microsoft last week released the Update Rollup 2 for System Center 2012 SP1 – Virtual Machine Manager which includes a lot of fixes and improvements. If you want to update you can do this by using the Windows Update scenario or install it manually.

You have to uninstall the Update Rollup 1 for SCVMM (you can find more on the reason on Carmen Summers blog post). Windows Update will not show you the Update Rollup to before you have uninstalled UR1.

If you have downloaded the Update Rollup 2 via the Windows Update Catalog and have installed it manually, it’s recommended that you uninstall UR2 first, after that uninstall UR1 and finally install UR2 on a System Center 2012 SP1 installation without any Update Rollups installed.

SCVMM Agent Update

After you have installed the Update Rollup 2 for Virtual Machine Manager, make sure you also update the Agents on the Hyper-V hosts.

VMM Agent Versions:

Update Rollup 1: 3.1.6011.0
Update Rollup 2: 3.1.6020.0

SCVMM Agent Version

Btw. Remember to do this not only for the VMM management server, don’t forget the hosts where the VMM console is installed, like System Center App Controller.

System Center 2012 SP1 Virtual Machine Manager Update Rollup 2 available

System Center Logo

Some days ago Microsoft announced the availability of System Center 2012 SP1 – Update Rollup 2, which included fixes for the whole System Center suite expect Virtual Machine Manager. Yesterday Carmen Summers wrote in her blog post that System Center 2012 SP1 Update Rollup 2 for Virtual Machine Manager is now available as well.

And KB2826405 and KB2826392 fixes around 20 issues with Virtual Machine Manager:

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.

Thanks to Michel Luescher (Consultant Microsoft Switzerland) for the info.

 

Cannot remove Hyper-V Host from SCVMM

System Center Logo

Today I run in to the problem where I could not remove a Hyper-V Hosts from System Center Virtual Machine Manager. The Hyper-V host was reinstalled before he was removed from SCVMM and the host was showing has HOSTNAME (pending) in the SCVMM Management Console. If you did a right click to remove the host, the Remove option was greyed out.

But don’t worry Windows PowerShell came to the rescue, with the following command you can remove the Hyper-V host from Virtual Machine Manager.


Get-SCVMHost <HOSTNAME> | Remove-SCVMHost -force

System Center 2012 SP1 – Virtual Machine Manager support for VMware vSphere ESX Hosts

System Center Logo

As System Center 2012 SP1 was released, it officially supported VMware vSphere 4.1 and 5.1, there was no support for vSphere 5.0 in SCVMM 2012 SP1. Now since a lot of customer have requested this feature, Microsoft added VMware vSphere 5.0 to the supported list of vSphere versions. For those who didn’t know that, to manage VMware ESX Hosts you need a version of vCenter. Some months ago I made a blog post about how you can add your VMware infrastructure to Virtual Machine Manager.

Virtual Machine Manager now supports the following versions of VMware vSphere:

vCenter Server:

For System Center 2012 – Virtual Machine Manager:

  • VMware vCenter Server 4.1

For VMM in System Center 2012 SP1:

  • VMware vCenter Server 4.1
  • VMware vCenter Server 5.0
  • VMware vCenter Server 5.1

Virtual machine hosts and host clusters that run any of the following versions of VMware:

For System Center 2012 – Virtual Machine Manager:

  • ESXi 4.1
  • ESX 4.1
  • ESXi 3.5
  • ESX 3.5

For VMM in System Center 2012 SP1:

  • ESXi 5.0
  • ESXi 5.1
  • ESXi 4.1
  • ESX 4.1

Get more information here: System Requirements: VMware ESX Hosts and here: System Requirements for System Center 2012 SP1.

 

Update Rollup 2 for System Center 2012 Service Pack 1

System Center Logo

Microsoft released Update Rollup 2 for System Center 2012 Service Pack 1 which includes updates for the System Center Suite. Get more information about the Update Rollup 2 for System Center 2012 Service Pack 1 on support.microsoft.com.

Hyper-V Converged Fabric with System Center 2012 SP1 – Virtual Machine Manager

System Center Logo

This blog post is a part of a series of blog posts about System Center 2012 Virtual Machine Manager, I am writing together with Michel Luescher (Consultant from Microsoft Switzerland).

Hyper-V Converged Fabric

Last year I already wrote a blog post about Windows Server 2012 Hyper-V Converged Fabric or Converged Networking. Hyper-V Converged Fabric in a simple way allows you to use network adapters for different type of traffic. In Windows Server 2008 R2 Hyper-V we didn’t really had this capabilities because the network teaming relied on 3rd party software and Hyper-V itself didn’t offered a mature QoS solution. In other words, we had to go with what I now would call a traditional Hyper-V host design.

Traditional Design

traditional Hyper-V host

Each dedicated Hyper-V network such as CSV communication or the Live Migration network used an own dedicated physical network interface. These different network interfaces could also be teamed with third party software, example with the software from HP, Broadcom or Intel. This design is still a good design in Windows Server 2012 but there are other configurations which are a lot more flexible.

In Windows Server 2012 you can get much more out of your network configuration. First of all NIC Teaming is now integrated and therefor out-of-the-box supported in Windows Server 2012. Another cool feature is the use of virtual network adapters in the Management OS (a.k.a. Parent Partition). This allows you to create a Hyper-V Hosts with all the necessary networks (Management, Live Migration, Cluster,…) by teaming just two or more physical adapters for a virtual switch and then create the additional virtual network adapters (vNICs) for the Hyper-V Management OS.

Continue reading

Poster: Networking in Virtual Machine Manager

Microsoft released a poster about networking options available in System Center Virtual Machine Manager 2012 SP1. I am sure there will be also an updated version of the Microsoft Server Posterpedia Windows 8 App really soon.

System Center Virtual machine Manager Networking Poster

This poster for VMM in System Center 2012 SP1 can help you:

  • Plan your VMM networks using a logical view of VM networks, logical networks, and logical switches using a variety of configurations including VLAN-based configuration, no isolation, network virtualization, external networks, and with no virtual networking.
  • Configure networking in VMM using configuration steps by roles including fabric administrators, tenant administrators, or by any user.
  • Understand the network object model with diagrams of objects showing the relationships between objects.
  • Extend VMM with options including using a vendor network-management server with extensions, connect a VM network to other networks by configuring the VM network with a gateway, and load-balance requests to VMs that make up a VMM service tier by adding a load balancer to VMM.

You can get the poster here: Poster: Networking in Virtual Machine Manager

Make sure you check out our latest blog posts about Hyper-V Networking in System Center Virtual Machine Manager 2012 SP1.

There is also a poster for Windows Server 2012 Hyper-V available: Windows Server 2012 Hyper-V Component Architecture Poster and Companion References