Check the CAU role configuration on each failover cluster. Run the following PowerShell command from a management server with the Failover Clustering tools installed:
Get-CauClusterRole -ClusterName <ClusterName>
If the cluster is configured for self-updating mode, this command returns the CAU clustered role details, including the update schedule and configuration. If the CAU role is not installed, the cluster is not self-updating and is likely being managed in remote-updating mode (where an administrator or management system runs CAU sessions manually). You can also confirm with:
Get-CauClusterRole -ClusterName <ClusterName> | Select-Object *
For remote updating, you would typically see no CAU clustered role installed, and updates are initiated with commands such as:
Invoke-CauRun -ClusterName <ClusterName>
To standardize all clusters, decide on one operating model. For self-updating, install and configure the CAU clustered role consistently:
Add-CauClusterRole -ClusterName <ClusterName> -MaxFailedNodes 1 -CauPluginName Microsoft.WindowsUpdatePlugin
Then set the same schedule, update plugin settings, and maintenance window across clusters. For remote updating, remove any CAU clustered roles:
Remove-CauClusterRole -ClusterName <ClusterName>
and manage updates through a centralized process (for example, Windows Admin Center, SCCM/MECM, Azure Update Manager, or scheduled Invoke-CauRun jobs). Also verify the CAU settings in Failover Cluster Manager under Cluster > Roles > Configure Cluster-Aware Updating.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin