Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

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

Full Stack Cluster-Aware Updating for Azure Stack HCI clusters using OpenManage Integration snap-in

Use full stack Cluster-Aware Updating capability in OpenManage Integration snap-in to perform hardware updates (firmware, BIOS, and drivers) on Dell Integrated System for Microsoft Azure Stack HCI (also known as Azure Stack HCI) cluster nodes in addition to the operating system update available in the Windows Admin Center.


Before you begin Firmware, BIOS, and Drivers update, verify the following prerequisites are met:
  • Ensure that you have installed the supported version of the Windows Admin Center.
  • You are logged in to Microsoft Windows Admin Center remotely using domain administrator credentials. Ensure the credentials are part of Gateway Administrator. For more information, see Microsoft documents.
  • Ensure that the Dell Integrated System for Microsoft Azure Stack HCI (also known as Azure Stack HCI) cluster is created from AX nodes that have Azure Stack HCI 21H2 or 22H2 operating systems installed.
  • Ensure OMIWAC Premium License is installed on each AX nodes.
  • Ensure that pre-update script and post-update script are not present as part of the cluster role. if it's present, it's recommended to remove the script before triggering Updates. For more information, see Tests Summary page in the Troubleshooting section.
  • To use online catalogs, ensure that both Windows Admin Center and Open manage Integration are connected to the Internet. You may also use proxy settings in both Windows Admin Center and Open manage Integration for generating compliance and update. For more information about proxy settings, see Configure proxy settings.
  • To use the offline DRM catalog, ensure that settings are configured as mentioned in the Configure update tool settings.
  • If the snap-in prompts to specify the "Manage as" credentials, provide appropriate cluster domain administrator credentials to authenticate to the managed node, and then select use these credentials for all connections check box. Ensure that the user is part of the local user group of gateway administrators. For more information, see Cluster-Aware Updating requirements and best practices in Microsoft document.

About this task

To get latest features, apply the latest security fixes, and keep the infrastructure defect free, you must ensure that the target nodes are updated with the latest operating system and hardware updates such as Firmware, BIOS, and Drivers. Many operating system and hardware updates may require rebooting nodes to apply the changes. The reboot process may impact the workload or applications running on the node.

With the use of OpenManage Integration snap-in integrated with the Windows Admin Center cluster update workflow, you can seamlessly update the firmware, BIOS, and drivers on cluster nodes in addition to the operating system update available in the Windows Admin Center. It also reduces the number of reboots required after the update using the Full Stack CAU feature.

To access full stack update feature, in Windows Admin Center, select Updates from the Tools menu.

To perform hardware updates on the cluster separately, use the Cluster-Aware Updating feature available in the OpenManage Integration with Windows Admin Center extension tool. See Update PowerEdge servers using OpenManage Integration extension.


To perform both operating system and hardware updates on Azure Stack HCI cluster nodes:

  1. In Windows Admin Center, select Updates from the Tools menu.
    1. You must enable Credential Security Service Provider (CredSSP) and provide explicit credentials. When asked if CredSSP should be enabled, click Yes.
    The Updates page appears.
  2. Select Quality updates only and then click Check for updates. Quality updates include both operating system and hardware updates.
    The Install updates page appears.
  3. For operating system update, see the Azure Stack HCI documentation in Microsoft.
  4. On the Install updates page, after you review the operating system updates, select Next: Hardware updates.
  5. Windows Admin Center will check if the supported Dell OpenManage Integration extension is installed.
    • If the extension is not installed, click Install to accept the license terms and install the Openmanage Integration snap-in.
    • If the latest OpenManage Integration extension is already installed or after the OpenManage Integration snap-in is installed, click Get updates to move to the Hardware updates page.
    After the OpenManage Integration snap-in is installed, the OpenManage Integration extension appears under the Tools menu in the Windows Admin Center. You will be able to use all the features of OpenManage Integration extension along with the snap-in specific features.
  6. In Update Checklist, OpenManage Integration extension reviews the necessary prerequisites required to install hardware updates.
    • If any of the prerequisite fails, a banner message appears. Click View Details to see the non-compliant prerequisites, and ways you can resolve them. Resolve the non-compliant prerequisites, and click Re-Run to run the prerequisite checks again. For more information about prerequisites check, see Prerequisites check details.
    • If all prerequisites are compliant, the extension will proceed to check the criteria listed on the "Update Checklist" page to ensure that all nodes are ready for update.
      • If any criteria fails, resolve issues by following the recommendations and then click Re-Run to run the checklist again.
      When finished, click Next: Update Source.
    NOTE: You must meet all the prerequisites mentioned on the "Update Checklist" tab, otherwise you cannot proceed to the next step.
  7. To generate compliance report against the validated Azure Stack HCI catalog, on the Update source page, do the following:
    1. Select one of the methods to download catalog files:
      • Online (HTTPs) - Update Catalog for Microsoft HCI Solutions to download the catalog automatically from the Online catalog option is selected by default.
        Online catalog support requires direct internet connectivity from the Windows Admin Center gateway. The overall download time of a catalog depends on the network bandwidth and number of components being updated.
        NOTE: Accessing to the Internet using proxy settings are not supported.
      • Offline - Dell Repository Manager Catalog to use the DRM catalog configured in a CIFS location.

        OMIMSWAC with or without Internet access allows you to select the Offline - Dell Repository Manager Catalog to generate compliance report. You may use this option when the Internet is not available or to use a customized DRM catalog.

        • To use offline catalog, select DRM Settings to ensure the CIFS share path is configured with the DRM catalog. To create a DRM catalog, see the Technical article.
    2. To use the Dell System Update (DSU) and Inventory Collector (IC) tools, select Advance setting, and then select one of the following:
      • "Automatically downloads and configures the Dell System Update (DSU) and Inventory Collector (IC)." when OMIMSWAC is connected to the Internet.
      • "Manually configure DSU and IC" and then select Settings to manually download and configure DSU and IC tools in a share location. We recommend using this option when OMIMSWAC is not connected to the Internet.

        DSU and IC settings, configured using Update Tool settings in OpenManage Integration extension will also be available under Advance setting in OpenManage Integration snap-in.

    When finished, click Next: Compliance report.
    OMIMSWAC downloads the catalog, collects the DSU and IC tools that are configured in the Settings tab, and generates a Compliance Report. If DSU and IC tools are not configured in the Settings, then OMIMSWAC downloads them from to generate the compliance report.
  8. On the Compliance report tab, view compliance report. Select the components that require an update and click Next: Summary.
  9. On the Summary tab, review the components to be updated, and then click Next: Download updates to download the updates for the selected components.
    1. After the updates are downloaded, if Kernel Soft Reboot is enabled on the cluster, the Disable Kernel Soft Reboot check box is displayed. To disable Kernel Soft Reboot only for this particular update operation, select the check box. For more information, see When to use Kernel Soft Reboot.
    NOTE: While the download is in progress, it is recommended not to exit or close the browser. If you close or exit the browser, download of update operation may fail.

    The download 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 download job is finished.

    • If the download operation fails, check the log files stored at the following path for troubleshooting.
      • 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
      • After the cluster update is over, DSU logs for individual nodes can be found in <Windows Directory>\Temp\OMIMSWAC folder on the respective nodes.
    • To run the compliance report again, click Re-run Compliance and repeat steps 4 to 7.
  10. After the updates are downloaded, follow the instructions on the Windows Admin Center to install both operating system and hardware updates.
    If the UI session is alive, node level progress status is displayed. Windows Admin Center notifies once the update is completed.


If any of the updates require a restart, nodes will be restarted one at a time, moving cluster roles such as VMs between nodes to prevent downtime.

Next steps

NOTE: The CAU clustered role is configured by default to trigger the self-updating functionality of the cluster on Tuesdays on the third week of each month. Therefore, after the update is complete, ensure to disable the CAU clustered role in one of the cluster node to prevent the self-updating functionality of the cluster. For more information about disabling CAU clustered role, see

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: <>()\