Before I can talk about anything else, I need to give CAU a brief introduction. Here are the three takeaways: In order to fully utiilize CAU, you have to install the full set of Failover Clustering tools on each node.
Simply, this tool manages Windows Updates for an entire cluster in a way that eliminates or reduces requirements for manual intervention and eliminates or reduces guest downtime. When you install Failover Clustering in Server Manager, it queries you to install the tools along with the feature.
If you missed it, you can go back in to the Add Roles and Features Wizard and select it under Remote Server Administration Tools.
If you don’t do that, then you can allow CAU to create the account.
I like creating it myself as CAU uses an automatically-generated name that probably won’t fit your naming scheme.
No matter what, you need to enable at least a few permissions.
In today’s data center, and for the foreseeable future, the biggest word is “automation”.
It doesn’t matter how big your datacenter is, either.
Whether your servers have a multi-continental presence or have been relegated to a closet, there’s never enough staff allocated with enough time to manually manage these systems.
Even if you did have the time, why would you want to?
What benefit is there in opening processes up to human error when you can have the systems babysit themselves?
That’s why I’m surprised that there’s so little written about Cluster-Aware Updating (CAU).