Dell EMC OpenManage Integration Version 1.1.0 with Microsoft Windows Admin Center User’s Guide

Step 3: Updating—Target node components in Failover Clusters and Azure Stack HCI

After generating the compliance report in the Compliance Details tab and confirming the components selection in the Summary tab, proceed to update the target node components in Failover Clusters and Azure Stack HCI as follows:

  1. To update the BIOS, driver, firmware, and/or system management application of target node components in Azure Stack HCI and Failover cluster to the latest version, under Summary, click Next: Cluster Aware Update.

    A message is prompted to enable CredSSP.

  2. Click Yes to enable the CredSSP and continue updating the selected components. You will be directed to the Update Status window.

    To improve security, disable the CredSSP after the update operation is complete.

    NOTE: While the update is in progress in the Update Status window, it is not recommended to exit or close the browser. If you close or exit the browser, cluster update may fail.

    The update job continues in the background regardless of whether the UI session is alive or not. If the UI session is alive, node level progress status is displayed. OMIMSWAC notifies once the update job is finished.

    • After successful update, compliance report (based on the previous selections) will be recomputed automatically and displayed in the Update tab.
    • If the update operation fails, check the log files stored at the following path for troubleshooting purposes.
      • Gateway system: <Windows Directory>\ServiceProfiles\NetworkService\AppData\Local\Temp\generated\logs
      • Windows 10 gateway system: <Windows installed drive>\Users\<user_name>\AppData\Local\Temp\generated\logs
    • To run the compliance report again, click Re-run Compliance and provide the compliance settings details.
NOTE: If an update job fails, the updated components will not be rolled back to the old version. Due to this, sometimes the BIOS, firmware, or driver version across nodes in the cluster will not be at the same level. In this case, rerun the update by excluding the updated component.

Rate this content

Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\