Tag: System Center 2012 SP1

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.

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

Speaking at the E2EVC in Copenhagen


Last year I was for the first time the Experts 2 Experts Virtualization Conference (E2EVC) in Hamburg where we teach a Microsoft MVP Master Class and also did a video interview (4 Virtual Machine MVPs talking about Hyper-V at the E2EVC).

The next E2EVC conference will take place in Copenhagen on the 30th May to 2th July. I have the chance to present a session with the title “SCVMM-Mania (should or should you not manage all your hypervisor platforms using SCVMM 2012 SP1)”  together with Michael Rüefli. The session will include content about System Center Virtual Machine Manager 2012 SP1 and how you can manage different hypervisors like Hyper-V, VMware ESXi and Cirtix XenServer.

And there a lot of top session form:

and a lot more…

Cisco announced Nexus 1000V for Hyper-V with Microsoft SCVMM integration

Cisco Nexus 1000v

It’s now early Saturday morning in Switzerland and I’m up because I had to go to university this morning and in the break I was checking my RSS feeds and saw two blog post from my Irish Microsoft MVP fellows Aidan Finn (MVP Virtual Machine) and Damian Flynn (MVP System Center Cloud & Datacenter Management) about the new Cisco Nexus 1000v for Hyper-V with Microsoft System Center Virtual Machine Manager integration.

What is the Cisco Nexus 1000v

Cisco Nexus 1000V Series Switches provide a comprehensive and extensible architectural platform for virtual machine (VM) and cloud networking. The switches are designed to accelerate server virtualization and multitenant cloud deployments in a secure and operationally transparent manner. Integrated into the Windows Server 2012 Extensible Switch, and fully compatible with System Center Virtual Machine Manager 2012 SP1, the Cisco Nexus 1000V Series provides:

  • Advanced virtual machine networking based on Cisco NX-OS operating system and IEEE 802.1Q switching technology
  • Cisco vPath technology for efficient and optimized integration of virtual network services
  • Tight integration with System Center Virtual Machine Manager 2012 SP1
  • Layer 2 Switching with Transmit side Rate Limiting
  • Security Policy Mobility, inbuilt support for Private VLANs with local PVLAN Enforcement
  • Provisioning Port Profiles with deep Integration with SCVMM
  • Traffic Visibility, including VM Migration Tracking, NetFlow v.9 with NDE, Cisco Discovery Protocol v.2
  • And more…

You can get more information in a Cisco WebEx Webcast about the Nexus 1000v.


System Center 2012 SP1 Configuration Analyzer

System Center Logo

Some days ago Microsoft released the System Center 2012 SP1 Configuration Analyzer which allows you to troubleshoot issues with the configuration of System Center 2012 SP1 server-side components.

The System Center 2012 SP1 Configuration Analyzer is your first line of defense in troubleshooting issues with System Center 2012 SP1 server-side components. The System Center 2012 SP1 Configuration Analyzer is a diagnostic tool that you can use to evaluate important configuration settings for computers that are running any of the following System Center 2012 SP1 components: Operations Manager, Virtual Machine Manager (VMM), Service Manager, Orchestrator (plus Service Provider Foundation), Configuration Manager, and Data Protection Manager (DPM).

Previously, users who wanted to take advantage of this functionality had to download and install best practice analyzers (BPAs) for each System Center component.  With the release of System Center 2012 SP1, users can now use a single model (called the System Center 2012 SP1 Configuration Analyzer) within Microsoft Baseline Configuration Analyzer 2.0 that automatically detects and scans all System Center 2012 SP1 server-side components.

Get the download here: System Center 2012 SP1 Configuration Analyzer

Thanks to Stefan Roth fellow from itnetx for sending the link.

Using System Center 2012 SP1 – Virtual Machine Manager Logical Switch with Hyper-V

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

In the last post we wrote about the new networking features in System Center 2012 SP1 – Virtual Machine Manager. One of the biggest changes in SCVMM is the concept of the Logical Switch. The new Logical Switch allows to manage Hyper-V Virtual Switches including the underlying network teaming centralized from System Center Virtual Machine Manager.

In Service Pack 1 you can choose between two Virtual Switches; You can use either the new Logical Switch or you can use the Standard Virtual Switch, which is basically the “legacy” Virtual Switch with the default Hyper-V Virtual Switch functions. If you create the Virtual Switch on a Hyper-V host you can choose between the two options and this allows you to choose the Logical Switch.

Standard Switch

The Standard Virtual Switch is basically the normal Hyper-V Virtual Switch and the configuration looks exactky the same as in the Hyper-V Manager. If you add a Hyper-V Host to SCVMM and you have previously created the Virtual Switch using Hyper-V Manager or PowerShell cmdlets, this Virtual Switch will be shown as Standard Switch.

Standard SwitchIn a nutshell:

  • The Standard Switch can only be deployed on one network adapter, so if you want to use network teaming you have to create the network teaming manual on the Hyper-V host.
  • The available Logical Networks have to be added on every host on the physical network adapter. This can be a little of a management effort but I made a simple PowerShell Script which helps you to do configuration changes: SCVMM 2012: Add Logical Network to all Hyper-V Hosts in HostGroup via PowerShell
  • Existing Virtual Switches will be shown as Standard Switches in SCVMM, you have to recreate the configuration if you want to use the Logical Switch.
  • With the Standard Switch you can set the one single management vNIC which can be used by the Management OS. You can attach additional vNIC using Windows PowerShell on the Hyper-V host but not from the Virtual Machine Manager Console

Logical Switch

A Logical Switch includes Virtual Switch Extensions, Uplink Port Profiles which define the physical network adapters used by the Hyper-V Virtual Switch for example for teaming and the Virtual Adapter Port Profiles mapped to Port Classifications which are the settings for the Virtual Network Adapters of the virtual machines.

Logical SwitchIn a nutshell:

  • The Logical Switch allows you to add multiple NICs in one Virtual Switch and creates a NIC teaming based on Uplink Port Profile. The Uplink Port Port Profile includes all the information which teaming mode and algorithm has to be used.
  • The Uplink Port Profile also includes a list of available logical network sites. If you have an additional Logical Network which runs on this network adapters you can simply add this to the Uplink Port Profile.
  • You can create multiple vNICs (vEthernet Adapters) for example a Hyper-V Converged Networking setup. Port Classifications and Virtual Adapter Port Profiles bring support for Bandwidth Management and QoS.
  • Logical Switches only work with windows Server 2012 , but there is no need to stay on Windows Server 2008 R2 Hyper-V.

If you are running Windows Server 2012 Hyper-V hosts there is no reason why you should not use the Logical Switch, which adds additional functionality and centralized management to the Hyper-V Virtual Switch.

You can find the German Version of this blog post on Michel Lueschers (Consultant Microsoft Switzerland) blog.