The box super updating
Remote-Updating: CAU can run on a standalone Windows 8/Windows Server 2012 computer that is not a cluster node.
As failover clusters are all about high availability of services hosted on the cluster, one would almost never patch all cluster nodes at the same time.For this blog post, I will focus on the first mode above: Self-Updating.The beauty of self-updating is that it lets you configure your failover cluster to be on “auto pilot” in terms of patching, and once set up, the cluster updates itself on the schedule you have defined in a way that it causes either no impact to service availability, or the least possible – depending on the types of workloads (e.g.Then look at the Cluster Action circled in green in the previous screen shot – “Configure cluster self-updating options”.This is the action you choose to start the self-updating configuration process for your failover cluster.Cluster-Aware Updating (CAU) is an exciting new feature that we have added in Windows Server 2012 that addresses precisely this gap.
Once you have decided to try the CAU feature in Windows Server 2012 to update your failover cluster, you will very quickly apreciate its simplicity and power.
It's easy to post questions about Windows 10, Win8.1, Win7, Surface, Office, or browse through our Forums.
Post anonymously or register for greater privileges.
CAU is cluster workload-agnostic, and it works great with Hyper-V, and a number of File Server workloads. Self-Updating: Once configured by you, CAU can run on a cluster node that it is meant to update.
You would simply configure the updating schedule and let CAU update the cluster 2.
If you plan to run CAU from a computer different from the cluster nodes, that is still easy!