Hyper-V Host Patching – Cluster Aware Updading vs. Virtual Machine Manager Fabric Patching

Posted on May 21, 2013 by Thomas Maurer

Windows Server 2012 Logo

In the past weeks I was giving a Windows Server 2012 Hyper-V workshop to customers and as we went to the Hyper-V host management I talked about how you can update your Hyper-V infrastructure and how you can automatically update your Hyper-V cluster.

If we do not think about System Center Orchestrator we have basically two solutions to fully upgrade our Hyper-V clusters first is the System Center Virtual Machine Manager Fabric Patching which is available since System Center 2012. The second one is a new one called Cluster Aware Updating which is included in Windows Server 2012.

Both solutions do basically the same thing and using the same concept:

Scanning the Hyper-V host for updates
Putting the first node in maintenance mode and pause the node in the cluster
Moving all virtual machines to other nodes of the cluster
Installing the patches
rebooting the server
checking if all services are up again
stop the maintenance mode
start doing the same with the next node

This is basically what both solutions are doing, but there are small differences between them and both have advantages and disadvantages.

Cluster Aware Updating (CAU)

Moving not only virtual machines to other nodes, it does also move other cluster roles and cluster disks to other nodes
Cluster Aware Updating can use different update sources (Windows Update, Microsoft Update, WSUS, SCCM,…)
You can apply hotfixes via CAU
Cluster Aware Updating has APIs for third party vendors
You can do driver or firmware updates via CAU
You can schedule it via Self-Updating mode
Run pre- and post-scripts
Update Approval process over WSUS or SCCM
Only supporting Windows Server 2012
Coordination via cluster role

System Center Virtual Machine Manager

Does only move virtual machines to other nodes
Needs a WSUS server where the updates come from
Only updates which can be installed via WSUS
Virtualization (Fabric) Administrator will create update baselines and approve updates
Not third-party integration
Log – logs which administrator approved the updates
Integration in System Center Operations Manager, sets host in maintenance mode on SCOM so no alerts are generated.
Role based update management
Supports Windows Server 2008, Windows Server 2008 R2 and Windows Server 2012 Hyper-V.
Coordination via Virtual Machine Manager

Both solution do a great job and can of course be extended by using Windows PowerShell, System Center Orchestrator or third-party products.

The two main differences are Windows Server 2012 Cluster Aware Updating is definitely the newer solution with extensibility for third-party solutions with support for other cluster roles not just Hyper-V. Where System Center Virtual Machine is the clear winner, is where you have security roles in place and you need logs and other security features. And System Center Virtual Machine Manager has also a connection to System Center Operations Manager which lets you set Hyper-V nodes to maintenance mode.

Virtual Machine Backup and Recovery: Five Critical Decisions

Posted on May 6, 2013 by Thomas Maurer

Together with Symantec, Mahmoud Magdy (Microsoft MVP for Exchange Server) and Mikko Nykyri (VMware vExpert) we produced a whitepaper called “Virtual Machine Backup and Recovery: Five Critical Decisions”. This whitepaper covers an overview about virtualization and the challenges which come with the new workloads in terms of backup and recovery.

Because of the outstanding economy, flexibility, and service levels it offers, virtualization is transforming data centers at breakneck speed: by 2016, an estimated 80 percent of the world’s x86 servers will be virtual machines (VMs).1 But the speed of this transformation, along with the high resource utilization, ease of cloning, moving workloads, and other ways virtualization works its magic, raise challenges for “traditional” IT services and the teams that deliver them. Nowhere is the complexity that virtualization creates for traditional IT services more apparent than in backup and recovery, which participants in a recent Symantec survey ranked among their least-successful IT initiatives. This paper addresses five critical decisions organizations must make when building a backup and recovery plan to:

Maintain protection, visibility, and control of applications and data.

Maximize utilization of established infrastructure, processes, staff, and budget.

Use virtualization to improve backup and recovery processes.

Create an efficient, scalable, future-prepared backup and recovery environment.

Each issue is presented first in general terms that apply across IT environments, and then add comments for specific platforms, applications, or industries based on our individual experience as VMware® vExperts and Microsoft® MVPs.

You can download the whitepaper here: Symantec Virtual Machine Backup and Recovery: Five Critical Decisions

Make also sure you checkout the Google Hangout event on Fri, May 10, 7:00 PM – 8:00 PM.

Join a panel of virtualization experts including Microsoft MVPs Mahmoud Magdy & Thomas Mauer and VMware vExpert Mikko Nykyri as they discuss the white paper they co-authored and offer their thoughts on the most important things to consider for a virtualized server environment.

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

Posted on April 29, 2013 by Thomas Maurer

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.

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

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

Posted on April 24, 2013 by Thomas Maurer

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

Posted on April 18, 2013 by Thomas Maurer

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

Migrate Hyper-V Cluster to Windows Server 2012 Hyper-V via Cluster Migration Wizard

Posted on April 17, 2013 by Thomas Maurer

Windows Server 2012 Logo

If you have already an existing Windows Server 2008 R2 Hyper-V cluster and you want to upgrade to Windows Server 2012 you have two options. The first one is by moving all virtual machines via System Center Virtual Machine Manager from the old Cluster into a new cluster. The second way to do it, is to use the Cluster Migration Wizard which is part of Windows Server 2012.

In my case I have two clusters one “old” Windows Server 2008 R2 Hyper-V cluster and my new Windows Server 2012 Hyper-V cluster. Both Clusters are fully configured and both have access to the same disks/LUNs. The disk and all the VMs are running on the old cluster.

On the new cluster you can start the Cluster Migration Wizard.

This will bring up the Cluster Migration Wizard. The wizard will ask you about the old cluster.

The Cluster Migration Wizard will scan the old cluster for CSVs and Cluster roles. You have to select the Cluster Shared Volume you want to migrate to the new cluster. Note: you can only migrate CSVs including all virtual machines running on this CSV and not just single virtual machines. If you want to migrate single virtual machines you could do a Hyper-V Export/Import or using System Center Virtual Machine Manager.

Since the Cluster Migration Wizard detects the roles as Hyper-V virtual machines he also asks for the new Hyper-V Virtual Switch.

You get a quick summary with all the information what the Migration Wizard will do, and you can migrate all roles. This means the Migration Wizard will create all cluster roles on the new cluster but will not take the existing VMs offline the VMs at this point are still running on the old cluster. You also get a Failover Cluster Migration Report at the end.

This report also shows you what’s next:

All the clustered services and applications selected for migration were migrated successfully. You may now take the clustered services and applications offline in your old cluster. Also take offline Cluster Shared Volumes used by any migrated roles, as well as storage pools for virtual disks used by any migrated roles. Then these disks, Cluster Shared Volumes, and clustered services and applications can be brought online in your new cluster.

In the new cluster you can now see the roles which are all turned of because there are still running on the old cluster. And you can also see the CSV which is offline on the new cluster and online on the old cluster.

As already mentioned we had no downtime until now. Now you can go and shutdown all the virtual machines running on your old cluster and take the migrated CSV offline.

Take the CSV offline

On the new cluster bring the CSV online

Bring the virtual machines on the new cluster back online.

And this is more how you can migrate a cluster. Remember there are still some tasks left.

Upgrade the Integration Components of all the virtual machines to the newest version.
Convert all VHDs to the new VHDX format to dynamic disks.
I also recommend that you use CSV Block Cache

There is also a great video from Symon Perriman and Rob Hindman, a Program Manager on the Windows Server Clustering & High-Availability team, in which they explain how you can upgrade to Windows Server 2012 Hyper-V.

Windows Azure: General Availability of Infrastructure as a Service (IaaS)

Posted on April 16, 2013 by Thomas Maurer

Today Microsoft announced the General Availability of the Windows Azure Infrastructure as a Service offering. This includes the new Virtual Machine and Virtual Network capabilities. This release is now live in production, backed by an enterprise SLA, supported by Microsoft Support, and is ready to use for production apps.

Today’s IaaS release also includes new enhancements:

VM Image Templates (including SQL Server, BizTalk Server, and SharePoint images)
VM Sizes (including Larger Memory Machines)
VM Prices (reduced prices 21%-33% for IaaS and PaaS VMs)

Windows Azure Infrastructure as a Service allows you to create Virtual Machine and Virtual Networks hosted by the Microsoft Windows Azure Cloud. I already created a blog post how you can create new Virtual Machines in Windows Azure and how you can connect System Center App Controller to manage your Private Cloud as well as your Public Cloud hosted in Windows Azure.

New Windows Azure Virtual Machine Compute Pricing

Below are the new hourly on-demand rates for Windows Azure Virtual Machines:

Size Name	# of CPU Cores	Memory	Windows VM Pricing	Linux VM Pricing
ExtraSmall	Shared	768 MB	$0.02 per hour	$0.02 per hour
Small	1	1.75 GB	$0.09 per hour	$0.06 per hour
Medium	2	3.5 GB	$0.18 per hour	$0.12 per hour
Large	4	7 GB	$0.36 per hour	$0.24 per hour
ExtraLarge	8	14 GB	$0.72 per hour	$0.48 per hour
A6	4	28 GB	$1.02 per hour	$0.82 per hour
A7	8	56 GB	$2.04 per hour	$1.64 per hour

Note that the above prices are for hourly on-demand usage (meaning there is no commitment to use them for more than an hour and you pay only for what you consume). Complete pricing details for Windows Azure Virtual Machines can be found here.

Commitment Pricing Discounts

You can also optionally take advantage of our 6 Month and 12 Month commitment plans to obtain significant discounts on the standard pay as you go rates. With a commitment plan you commit to spend a certain amount of money each month and in return we give you a discount on any Windows Azure resource you use that money on (and the more money you commit to use the bigger the discount we give).

You can get more information on the blog post from Scott Guthrie or the Windows Azure homepage.