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 PowerEdge servers using OpenManage Integration extension

Use OpenManage Integration with Windows Admin Center extension to view compliance reports and update PowerEdge server components such as BIOS, driver, firmware, and/or system management application.


Before you generate a compliance report and update components, ensure the following:
  • Ensure to comply with the software and hardware requirements listed in the compatibility matrix of the Installation Guide.
  • If the extension prompts to specify the "Manage as" credentials, ensure that you select Manage as and provide appropriate Server Administrator or Cluster Administrator accounts. 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.
  • Take care of the workload before updating the target node.
  • Ensure that inventory information for the target node has been retrieved.
  • Ensure that iDRAC lockdown mode is disabled. To disable iDRAC system lockdown mode in PowerEdge servers with iDRAC firmware lower than, see iDRAC documents.
  • For SAS-RAID_Driver, ensure the followings:
    • Set the SATA controller to RAID mode.
    • Set the NVMe PCIe SSDs to RAID mode.

      For more information about setting the RAID mode, see Appendix

  • Ensure the target node is not part of any HCI cluster. To update such nodes, connect to the cluster and use Cluster-Aware Updating feature.
  • Ensure that the WAC is not installed on the target node you want to update. To support this scenario, install the WAC on another target node (non WAC related) and complete the update.
  • Ensure that the target node is reachable using IP address, hostname, and Fully Qualified Domain Name (FQDN) of the target node.
    NOTE: If the target node is not reachable, and the target node update is performed, the update status may show failed. In this case, if you reboot the target node immediately after update and rerun the compliance, the target node components status may show compliant.
NOTE: We highly recommend to run only one compliance/update for a target node at a time. Running multiple compliance/updates at the same time might cause failures to the existing compliance/updates.

About this task

You can either use an online or offline catalog to generate compliance details and update components. In the Notifications section of the Windows Admin center, a notification appears when a new online or offline catalog file is available. To generate compliance report and perform firmware, BIOS, and drivers update for target nodes, do the following:


  1. Log in to Windows Admin Center and launch OpenManage Integration extension.
  2. Click View > Compliance. Hardware Compliance Summary page appears. Alternatively, go to the Action menu, under HARDWARE COMPLIANCE AND REMEDIATION, click Check Compliance.
  3. To generate a new compliance report against a validated catalog, click Check Compliance, and select a catalog from the Update Source as follows. By default, an applicable online catalog is selected based on the server.
    • To download the catalog automatically from, select Online (HTTPs) - <catalog name>. You can use the online catalog when the OpenManage Integration extension is connected to the Internet. You can also access the Internet using proxy settings. See configure proxy settings.
      The available online catalogs are:
      • For PowerEdge servers: Dell Enterprise Catalog which contains the validated versions of components for PowerEdge servers.
      • For MX servers: Dell MX Solution Catalog which contains the validated versions of components for PowerEdge MX Modular.
      • For AX nodes and Storage Spaces Direct Ready Nodes: Update Catalog for Microsoft HCI solutions.
    • To use the DRM catalog that is configured in a CIFS location, select Offline-Dell Repository Manager Catalog.
      You can select the offline catalog wit or without Internet connection to generate a compliance report. You can also use the offline catalog for customized DRM catalog.
      1. To use offline DRM catalog, ensure the latest catalog files are generated by using the Dell Repository Manager (DRM) application. The supported version of DRM application can be downloaded from Dell Repository Manager. To create a DRM catalog, refer to the Technical article.
      2. If the DRM catalog is created and stored in a share path, select DRM Settings and specify the CIFS share path where DRM catalog is located and provide credentials to access the share path.
  4. If the extension is not connected to the Internet, click Configure DSU and IC to Configure Dell System Update (DSU) and Inventory Collector (IC) tools. The extension uses DSU and IC tools to generate the latest compliance report.
  5. When finished, click Check Compliance.
    The extension downloads the catalog, collects the DSU and IC tools that are configured, and generates a Compliance Report. If DSU and IC tools are not configured manually, then the extension downloads them from to generate a compliance report.
  6. View the compliance report that is generated and displayed in the Harware Compliance Summary page. Click View Report to view component level compliance information. Click Export Report to export the compliance report in .csv format.
  7. To select the non-compliant components for update, click Fix Compliance. By default, the components that require update are selected.
    You may deselect the selected components or select the 'non-compliant' 'downgradable' components for update. However, if you want to change any of the default selections, ensure that the dependencies between the corresponding component firmware and drivers are met.

    For more specific selection, you can select each color code present under the bar chart or use the search box to filter out the required components. Select 'clear' at the upper right of the "Compliance Report" pane to remove the color code filter.

  8. When finished, click Update. If infrastructure lock is enabled, a pop-up appears, click Disable to disable the lock and update the components.
    The operation will enable the CredSSP automatically. To improve the security, disable the CredSSP after the operation is complete.
  9. OpenManage Integration extension checks the necessary prerequisites required to complete the update job. If all prerequisites are compliant, the extension will proceed to update the components.
    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. The extension notifies once the update job is finished.
    NOTE: If any component update requires a restart, the server will restart.
  10. 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 try the operation again. For more information about prerequisites check, see Prerequisites check details.
    If the update operation fails, check the log files stored at the following path for more details.
    • 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
    NOTE: While the update is in progress, do not exit or close the browser. If you close or exit the browser, node updates may fail and the update status may not be shown.

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