Configure the Fabric (27%)
Managing Fabric Updates in VMM
Windows Server Update Services (WSUS) 3.0 SP2 can be added to VMM to automate the patching of Hyper-V hosts and clusters. WSUS can be installed on the same server as Virtual Machine Manager (VMM) or on a different server. Installing WSUS on a different server is recommended when VMM is installed in a Highly-Available (HA) configuration. If WSUS is installed on a separate server, the WSUS console must be installed on the VMM server/s and the VMM service must be restarted.
How to Install WSUS for VMM
This process will cover how to install and configure WSUS for dedicated use by VMM.
Install WSUS Pre-requisites:
Download and install WSUS 3.0 SP2
Download Link: http://www.microsoft.com/en-us/download/details.aspx?id=5216
Select the Products that are applicable to VMM and Hyper-V Hosts
We’re using a remote WSUS Server, so to prepare the VMM Server we need to install the WSUS Console and restart the VMM Service (I just restarted the server instead).
How to Add the WSUS Server to VMM
Updating WSUS Settings
Once a WSUS Server has been added to VMM, you should only manage the WSUS Server from VMM. To view and change settings, right-click the server and select properties.
Configuring an Update Baseline
After you've added a WSUS Server to VMM. Update management is performed by configuring update baselines. An update baseline is a set of updates with a scope e.g. Host, Host Group. Hosts are scanned for compliance and brought into compliance through remediation.
There are two sample baselines, but we won’t be using those, we're going to configure our own (see below for the sample baselines.
Let's create our own.
After clicking finish, you will need to accept the EULAs that apply to any updates. If you have any issues with an update, I suggest you remove it and add it to the baseline at a later stage (for example, once the EULA has been downloaded).
Scan for Compliance
Remediate Compliance Issues