Take the time to create a prestaged computer account with a name that will mean something to you and your colleagues in a year’s time.
If all goes well the wizard will complete with a Success status.
Launch the Cluster-Aware Updating Wizard and then run Apply Updates To This Cluster.
The status of the update job will be visible under Log Of Updates In Progress.
You can also run Generate Report On Past Updating Runs from a specific time window, with the added option of exporting the report in HTML format.
The recommended managed solution will be to use WSUS.
If you are downloading updates through a proxy (such as directly from Microsoft) then you will need to configure Win HTTP proxy settings on each cluster node.
This would be done as follows, with a proxy called The Proxy. Internal that operates on TCP 80: netsh winhttp set proxy The Proxy. Internal:80 “ CAU will require a computer account that will be used by the cluster to create a HA role that enables the cluster to self-manage the orchestrated patching, even if the nodes of the cluster are being rebooted.
The setup wizard does allow you to let the cluster create a computer account in Active Directory, but this will get some anonymous name.
Windows Server 2012 (WS2012) introduced Cluster-Aware Updating (CAU) to allow each member of a cluster be paused, drained of highly available (HA) roles, patched, and rebooted in an orchestrated manner.
Without CAU, you will probably be patching your clusters manually (which rarely happens), and in the case of Hyper-V clusters, CAU will leverage Live Migration to ensure that services have zero downtime.
You will need a location for your nodes from which to download the updates.
Unfortunately System Center Configuration Manager does not support CAU yet.