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 nodes of Windows Server HCI, Azure Stack HCI, and Failover clusters using OpenManage Integration extension

The Cluster-Aware Updating (CAU) feature in OpenManage Integration with Windows Admin Center (OMIMSWAC) extension allows you to view the compliance report (firmware, BIOS, and drivers) and update the components of nodes of HCI and failover clusters without affecting the workloads.

Prerequisites

Before you generate a compliance report and update components, ensure the following:
  • Ensure to access the Windows Admin Center remotely using domain user credentials. Otherwise, use local administrator credentials to access the WAC locally. For more information, see Microsoft documents.
  • As OMIMSWAC uses the Microsoft Cluster-Aware Updating feature framework to perform cluster updates, ensure the Failover Clustering feature and Failover Clustering Tools are installed on all the target nodes before triggering CAU. For more information, see Cluster-Aware Updating requirements and best practices in Microsoft document.
    NOTE It is recommended to test the cluster readiness before triggering CAU. For more information, see Tests for cluster updating readiness in Microsoft document.
  • Ensure to comply with the software and hardware requirements listed in the compatibility matrix of the Installation Guide.
  • Ensure that OMIWAC premium licenses are installed on all cluster nodes to use the CAU feature. To verify licensing, click the iDRAC tab in the OpenManage Integration extension to view licenses installed on each node.
  • Ensure that the cluster service is up before running the update compliance. When the cluster service is down, an update compliance report for a target node may not be generated.
  • To manage a cluster, connect to the cluster using Manage as option and provide appropriate cluster domain administrator credentials. And 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.
  • Ensure that inventory information for the target node has been retrieved.
  • Ensure both physical, and virtual disks are in healthy state before triggering CAU.
  • 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 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 server update status may still show failed.

About this task

The CAU feature is supported for the following platforms with valid OMIWAC Premium Licenses:
  • YX4X models of Dell EMC PowerEdge Server and above with iDRAC firmware 4.00.00.00 or newer.
  • AX nodes and Storage Space Direct Ready Nodes with iDRAC firmware 4.00.00.00 or newer.
NOTE
  • We recommend to validate the cluster before triggering the CAU. For more information about validating a cluster, see Microsoft documents Validate Hardware for a cluster.
  • Updating a cluster where WAC is installed on a cluster node is not recommended. To support this scenario, install the WAC on another system that is not part of the cluster and complete the update.
  • We highly recommend to run only one compliance/update for a target node or cluster at a time. Running multiple compliance/updates at the same time might cause failures to the existing compliance/updates.
  • The CAU feature is not supported for YX2X and YX3X models of Dell EMC PowerEdge servers.

Steps

To generate compliance report and perform firmware, BIOS, and drivers update for Windows Server HCI, Azure Stack HCI, and Failover clusters, do the following:

  1. To generate compliance report against the validated catalog, on the Update source tab, do the following:
    1. Select one of the methods to download catalog files:
      • Online (HTTPs) - <catalog name> catalog to download the catalog automatically from dell.com. Online catalog is selected by default.
        The available catalogs are:
        • For PowerEdge servers and clusters containing 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 Windows Server HCI and Azure Stack HCI cluster nodes: Update Catalog for Microsoft HCI solutions which contains the validated versions of components for AX nodes and Storage Spaces Direct Ready Nodes.

        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. You can also access the Internet using proxy settings. See configure proxy settings.

      • 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 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. The supported version of DRM application can be downloaded from Dell EMC Repository Manager. To create a DRM catalog, refer to the Technical article.
        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 the Dell EMC System Update (DSU) and Inventory Collector (IC) tools, select Advance setting, and then select 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.

        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 https://downloads.dell.com to generate the compliance report.
  2. On the Compliance report tab, view the compliance report. For more information about the compliance report, view the compliance report.
    • The 'upgradable' components that are 'non-compliant' are selected by default for update.

      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.

      You can also click 'Expand all' icon at the upper right of the Compliance Report pane to expand the nodes where you can select or deselect components.

    When finished, click Next: Summary.

  3. On the Summary tab, review the components to be updated and choose to run the update now or schedule for later:
    • Run now: This will execute the cluster update immediately and reboot nodes if required.
    • Schedule later: Select a future date and time when the cluster update will be performed. This will download and copy the required files and keep the cluster ready for update at the specified time.

      At any given time, only one CAU job can be scheduled per cluster. Any new CAU job (Run now or Schedule later) will replace the existing scheduled job.

    To change the components selection, select 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.
    NOTE If a catalog does not contain updates to a component, then the component will not be displayed in the compliance report generated by using OpenManage Integration with Microsoft Windows Admin Center integration.
  4. When finished, click Next: Cluster Aware Update.
    A message is prompted to enable CredSSP. Click Yes to enable the CredSSP and continue updating the selected components. You will be directed to the Cluster aware update tab to see the update status. To improve security, disable the CredSSP after the update operation is complete.
    NOTE While the update is in progress on the Cluster aware 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.
    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
      • After the scheduled 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 provide the compliance settings details if required.

Results

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

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