How to Perform Rolling Updates on a Hyper-V Host Cluster in VMM
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Virtual Machine Manager, System Center 2012 R2 Virtual Machine Manager, System Center 2012 - Virtual Machine Manager
Use the following procedure to orchestrate rolling updates of a Hyper-V host cluster that is managed by Virtual Machine Manager (VMM). VMM rolls through the host cluster, remediating one cluster node at a time. If a cluster node is compliant, VMM bypasses that node.
Before VMM begins remediating a host in a cluster, it places the host in maintenance mode. You have the option of migrating all virtual machines to other hosts in the cluster. If you do not select this option, VMM saves state and does not migrate virtual machines.
The Remediate action is only available after you install a WSUS server for VMM, enable update management, create update baselines for computers managed by VMM, and scan the computers for compliance. For more information, see Managing Fabric Updates in VMM.
Display Compliance view for the managed computers:
Open the Fabric workspace.
In the Fabric pane, click Servers.
On the Home tab, in the Show group, click Compliance.
On the Home tab, in the Compliance group, click Remediate. (The Remediate task is only available when the selected objects are noncompliant.)
The Update Remediation dialog box opens.
In the resource list, select the host cluster by its cluster name.
If you select the cluster by its cluster name, VMM assumes you want to orchestrate remediation of the hosts in the cluster, and displays cluster remediation options. If you select individual hosts in the cluster, VMM assumes that you want to update them as you would a stand-alone host, and does not display cluster remediation options.
If you prefer to restart the computers manually after remediation completes if any updates require a restart, select the Do not restart the servers after remediation check box.
If you choose to manually restart computers after installing updates, the status of the computers will remain Pending Reboot until after you scan the computer for updates again. VMM does not scan computers to assess their update compliance status during refreshes.
Select the Allow remediation of clusters with nodes already in maintenance mode check box if you want to bypass maintenance mode.
By default, VMM places each host in maintenance mode before it remediates updates on the host.
Specify Live migration to remove virtual machines from a host before performing update remediation or Save state to shut down virtual machines and proceed with remediation.
Click Remediate to start update remediation on the host cluster.
You can watch the status of the remediation in the Jobs window or the Jobs workspace.
After the remediation completes successfully, and no reboot is pending for any computer, the compliance status of each node in the host cluster changes to Compliant.
If any computer has a Machine Reboot Pending status, restart the computer to complete the update installation and bring the computer into compliance.