How can we confirm whether CAU is operating in orchestrator mode or self-updating mode ?

Arjun Reddy 20 Reputation points
2026-07-31T05:27:51.09+00:00

We're reviewing the cluster-aware updating configuration on our failover cluster and have noticed inconsistent update behavior. Some updates appear to run automatically, while others require manual intervention, so we're unsure whether the cluster is configured for self-updating or remote-updating mode. How we can verify the active CAU mode and standardize the configuration across all of our clusters ?

Windows for business | Windows 365 Business
0 comments No comments

2 answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Marcin Policht 101.2K Reputation points MVP Volunteer Moderator
    2026-07-31T11:26:41.8533333+00:00

    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

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.