Users Guide

Compliance report page on loading state for a long time
While generating a compliance report, the compliance report page may show up in the loading state even after the notification
of successfully generated update compliance report.
In this case, go to any of the other tabs such as "Settngs", "Inventory", and so forth,, and then go back to the Update tab,
where you will see the generated compliance report.
Job failed while updating the selected components
Sometimes, CAU or target node updates may fail due to various reasons. The causes and resolutions are given below:
● Causes: If target nodes are not validated before triggering CAU, the CAU may fail.
Resolution: For Cluster-Aware Updating, ensure to validate the cluster before triggering CAU. For more information about
validating a cluster, see Microsoft document Validate Hardware for a cluster.
● Causes: If Failover Clustering feature and Failover Clustering Tools are not installed on target nodes, the CAU may fail.
Resolution: As OMIMSWAC uses the Microsoft Cluster-Aware Updating feature framework to perform cluster updates,
before updating a cluster using OMIMSWAC, ensure that the Failover Clustering feature and Failover Clustering Tools are
installed on all the target nodes. For more information, see CAU requirements and best practices in Microsoft documents.
To check whether failover clustering tools are running on all the target nodes, from the PowerShell window on the target
node, run the Get-CauClusterRole PowerShell command.
● Cause: Compliance Inventory file is not available for some nodes or file copying from node to gateway is failed after
compliance generation.
Resolution: Rerun the compliance.
● Cause: Due to Internet connectivity issue, the followings may fail:
○ Signature verification of DSU or IC
○ Downloading of online catalog
○ Downloading of DUP
If any of the above fails, CAU or server update also fails.
Resolution: Ensure that there is Internet connectivity and rerun compliance and update.
● Cause: DSU installer is not cleared from a node because the installer file sometimes gets locked by the Windows Admin
Center process (sme.exe).
Resolution: Restart the Windows Admin Center service from Windows Services consoles.
● Cause: CAU fails if any of the disks is not in healthy state.
Resolution: Ensure both physical and virtual disks are in healthy state before triggering CAU. If any disk is in an unhealthy
healthy state, see the Microsoft document to get it to a healthy state.
● Cause: CAU fails if any of the cluster nodes is paused.
Resolution: Resume cluster nodes (Failover roles) before triggering CAU.
● Cause: CAU fails when Failover Clustering feature and Failover Clustering Tools are not installed on all the target nodes.
Resolution: Ensure Failover Clustering feature and Failover Clustering Tools are installed on all the target nodes before
performing CAU. For more information, see https://docs.microsoft.com/en-us/windows-server/failover-clustering/cluster-
aware-updating-requirements.
CredSSP Failure
Check the event viewer logs in the gateway system to ensure that CredSSP has not failed during Cluster-Aware Updating. If the
CredSSP fails, following are the probable causes and solutions:
● Cause: While updating a cluster, credential delegation using CredSSP may fail.
Resolution: Reconnect the cluster using fully qualified domain name, and click Use this credential for all servers check
box.
For example, if the domain name is test.dev.com, use test.dev.com\administrator as the domain name, and then
click Use this credential for all servers check box.
50
Troubleshooting and Frequently asked questions