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 EMC OpenManage Integration Version 2.0 with Microsoft Windows Admin Center User’s Guide

Update target nodes using OpenManage Integration extension

By using OpenManage Integration with Windows Admin Center extension, you can view the compliance report (BIOS, driver, firmware, and/or system management application) and update the components of a target node.

Prerequisites

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, 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 that the WAC is not installed on the target node you want to 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, whereas the overall target node update status may still show failed.
NOTE
  • Updating a target node where WAC is installed is not recommended. To support this scenario, install the WAC on another target node (non WAC related) and complete the update.
  • 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.

Steps

To generate compliance report and perform firmware, BIOS, and drivers update for target nodes, do the following:

  1. To generate a compliance report against a validated catalog, select Update > Update Source, and choose any of the available offline or online catalog options as follows. The corresponding online catalog is selected by default based on the target node.
    • Choose 'Online (HTTPs) - <catalog name>' to download the catalog automatically from dell.com. Online catalog is selected by default. You can use the online catalog when the OMIMSWAC is connected to the Internet. You can also access the Internet using proxy settings. See configure proxy settings.
      The available catalogs are:
      • For PowerEdge servers: Dell EMC Enterprise Catalog which contains the validated versions of components for PowerEdge servers.
      • For MX servers: Dell EMC 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.
    • Choose "Offline - Dell EMC 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 EMC Repository Manager Catalog to generate a compliance report. You may use this catalog when the Internet is not available or to use a customized DRM catalog.
      1. To use offline DRM catalog, ensure the latest catalog files are generated by using the Dell EMC Repository Manager (DRM) application. The supported version of DRM application can be downloaded from Dell EMC Repository Manager. To create a DRM catalog, refer to the Technical article.
      2. After 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.
      NOTE
      • We recommend to use 'Update Catalog for Microsoft HCI solutions' catalog for Azure Stack HCI and Windows Server HCI.
      • You must provide individual catalog files with the user credentials for server manager, and cluster manager respectively.
  2. To use Dell EMC System Update (DSU) and Inventory Collector (IC) tools, select Advance settings and then choose one of the following:
    • " Automatically downloads and configures the Dell EMC System Update (DSU) and Inventory Collector (IC)." when OMIMSWAC is connected to the Internet. This is selected by default.
    • "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.

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

    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 https://downloads.dell.com to generate the compliance report.
  3. On the Compliance report tab, view the compliance report.
    • By default, all the 'non-compliant' 'upgradable' components are selected whose firmware, BIOS, or drivers will be updated.

      You may deselect the selected components or select the 'non-compliant' 'downgradable' components for update. However, 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.

    When finished, click Next: Summary.

  4. On the Summary tab, review the components to be updated and click Next: Update.
    • To change the components selection, click Back to go to the Compliance report tab, and select or clear the component selections.
    • If you want to change the update source and rerun the compliance, click Exit to go to the Update Source.
    While the update is in progress on the Update tab, 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.
    NOTE When components are selected and confirmed, if lockdown mode is enabled in iDRAC on the target node, an error occurs and you cannot proceed to update. Disable the lockdown mode on the target node that is being managed by OMIMSWAC before updating the target node. To disable iDRAC system lockdown mode, see iDRAC documents.
    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 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
    • To run the compliance report again, click Re-run Compliance and provide the compliance settings details.

Results

If any of the component update requires a restart, the node will be restarted.

Rate this content

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