How to Remediate Updates on a Stand-Alone Hyper-V Host 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 remediate updates for stand-alone Hyper-V hosts that are managed by Virtual Machine Manager (VMM). You can also orchestrate updates of a managed Hyper-V host cluster in VMM. For information, see How to Perform Rolling Updates on a Hyper-V Host Cluster in VMM.

System_CAPS_ICON_note.jpg Note

The Remediate action is only available after you install a WSUS server for VMM, enable update management, create and assign update baselines for computers managed by VMM, and scan the computers for compliance. For more information, see Managing Fabric Updates in VMM.

To remediate updates for a Hyper-V host in VMM

  1. Display Compliance view for the managed computers:

    1. Open the Fabric workspace.

    2. In the Fabric pane, click Servers.

    3. On the Home tab, in the Show group, click Compliance.

  2. Select the computers that you want to remediate. Click a computer to display all the baselines checked for that computer.

    The system may be compliant for some baselines and not compliant for others.You can select a single update baseline or a single update within a baseline.

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

  4. Optionally select or clear update baselines or individual updates to determine which updates to remediate. If you selected a computer to remediate, all updates are initially selected.

  5. If you prefer to restart the computers manually after remediation completes instead of letting the wizard do that, select the Do not restart the servers after remediation check box.

    By default, the wizard restarts the computer after installing updates if any of the updates requires a restart. If you choose not to restart the servers after remediation, and any updates require a restart, the operational status of the computer changes to Pending Machine Reboot after the remediation. The updates will not be activated until you restart the computer.

    System_CAPS_ICON_note.jpg Note

    If you choose to manually restart computers after installing updates, that 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.

  6. Click Remediate to start update remediation.

Performing Update Remediation in VMM