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

Update standalone nodes before deploying an Azure Stack HCI cluster using OpenManage Integration snap-in

The Integrated cluster deploy and update feature in OpenManage Integration enables you to update target nodes while creating an Azure Stack HCI cluster using Windows Admin Center. This feature also helps you to comply hardware configurations of selected nodes with Dell recommended hardware configurations.


Before you begin, verify the followings:
  • 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 all the prerequisites mentioned in the Create an Azure Stack HCI cluster using Windows Admin Center in the Microsoft documents are met.
  • Ensure that all the selected nodes are of AX nodes that have Azure Stack HCI 21H2 or 22H2 OS installed on it. For more information about the supported hardware, see Compatibility matrix.
  • To create a cluster, connect to the nodes by specifying appropriate node administrator credentials. And ensure that the user is part of the local user group of gateway administrators. For more information about selecting "Manage as", see the "Get Started with Windows Admin Center" section in the Microsoft documentation.
  • For HCI Configuration Profile checks, ensure OMIWAC Premium License for MSFT HCI Solutions is available on each node.
  • 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.

About this task

While deploying an Azure Stack HCI cluster using AX nodes in Windows Admin Center, use OpenManage Integration snap-in to ensure the followings for optimal cluster performance and support:
  • HCI Configuration Profile checks: ensures nodes selected for an Azure Stack HCI cluster are supported and have symmetrical hardware configurations as recommended by Dell.
  • Update: ensures Firmware, BIOS, and Drivers of selected nodes are the latest.
  • If any of the above prerequisites are not met, ensure to review and resolve as needed. You can also skip the OpenManage Integration snap-in flow and continue with the cluster creation workflow of Microsoft. However, skipping the Install hardware updates workflow may impact the cluster performance. Therefore, it is recommended to install hardware updates while creating clusters.
  • Dell OpenManage Integration with Windows Admin Center does not support the creation of a Stretched Cluster.
  • As this feature is integrated with the Azure Stack HCI cluster creation workflow, nodes will be restarted only once if necessary after both operating system and hardware updates are complete.

To update standalone nodes during Azure Stack HCI deployment, do the followings


  1. When deploying an Azure Stack HCI cluster in Windows Admin Center, using Get started wizard, complete the operations on the 1.1 Check the prerequisites, 1.2 Add servers, 1.3 Join a domain, 1.4 Install features, and 1.5 Install updates tabs as required.
    NOTE: Renaming nodes in 1.3 Join a domain tab is not supported and may cause prerequisites failure when installing hardware updates. To rename the servers (if required), it is recommended to do it outside of cluster deployment workflow. For example, use Azure Stack HCI OS Server Configuration tool (Sconfig) or Windows Admin Center to rename a node. Before launching the cluster create wizard, ensure the new node name is effective.
  2. On Install hardware updates tab, click Install to install OpenManage Integration snap-in. If you have already installed the latest OpenManage Integration extension version, click Check for updates to move to the install hardware updates page.
    NOTE: If the snap-in prompts to specify the "Manage as" credentials, ensure that you select Manage as and provide appropriate cluster 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 about selecting "Manage as", see the Get Started with Windows Admin Center section in the Microsoft documentation.
    When the OpenManage Integration snap-in is installed, the OpenManage Integration standalone 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.
  3. 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 HCI configuration profile checks and 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: HCI Configuration Profile.
    • If any of the nodes is not a valid model, you cannot proceed to the next step. For more information about supported models, refer to AS HCI support matrix.
    • If any of the nodes do not contain OMIWAC Premium License, you can continue to update nodes; however, you cannot run HCI Configuration Profile checks.
  4. For HCI Configuration Profile, review the configurations listed under each category to ensure all nodes configurations are as per Dell recommended configurations. For more information about hardware configurations required for HCI Configuration Profile, see HCI configuration profile.
    • (optional) If internet connection is not available, perform the below steps to run HCI configuration profile checks in offline mode:
      1. Download the asHCISolutionSupportMatrix.json and asHCISolutionSupportMatrix.json.sign files from
      2. Place these files in C:\Users\Dell\SymmetryCheck folder in the gateway system where Windows Admin Center is installed.
      3. Run the HCI configuration profile check.
    NOTE: HCI configuration profile will fail if any of the required configurations fail with a "Critical" error. Review the recommendations and details to resolve any issues to achieve HCI configuration profile and proceed to the next step.

    When the configuration fails with a "Warning", this means the configuration can be supported for cluster deployment, but could result in sub-optimal cluster performance. Therefore, it should be reviewed.

    click Re-Run to run the HCI configuration profile check again.

    When finished, click Next: Update source.
  5. 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 catalog to download the catalog automatically from Online catalog 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.
  6. On the Compliance report tab, view compliance report. Select the component that requires an update and click Next: Summary.
  7. On the Summary tab, review the components to be updated, and then click Next: Update to update the cluster nodes.
    A message is prompted to enable CredSSP.
    1. Click Yes to enable the CredSSP to continue updating the selected components. You will be directed to the Update page. To improve security, disable the CredSSP after the update operation is complete.
    NOTE: While the update is in progress on the Update page, it is recommended not to exit or close the browser. If you close or exit the browser, node updates may fail and the update status may not be shown.

    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.

    • If the update operation fails, check the log files that are 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 if required.


After hardware updates are complete, you may continue to follow the instructions shown on the Windows Admin Center to create the Azure Stack HCI cluster.

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