Dell EMC OpenManage Integration Version 1.1.1 with Microsoft Windows Admin Center User’s Guide August 2020 Rev.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2019 - 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: Overview of OpenManage Integration with Microsoft Windows Admin Center......................5 New in this release................................................................................................................................................................ 5 Additional resources..............................................................................................................................................................
Component showing non-compliant after update.................................................................................................... 30 OpenManage Integration access denied.................................................................................................................... 30 Dell Update Package failures........................................................................................................................................
1 Overview of OpenManage Integration with Microsoft Windows Admin Center Dell EMC OpenManage Integration with Microsoft Windows Admin Center (OMIMSWAC) enables IT administrators to manage the PowerEdge servers as hosts, Microsoft Failover Clusters created with PowerEdge servers, and Hyper-Converged Infrastructure (HCI) created by using the Dell EMC Solution for Microsoft Azure Stack HCI (Storage Space Direct Ready Nodes or AX nodes).
○ Allows generating compliance report for target nodes or clusters connected using a password that contains certain special characters. • In previous release, compliance generation failed when a server or cluster was connected using a password that contains special characters such as double-quote ("), grave accent (`), and semi-colon (;). Reset of CauClusterRole parameter to allow the self-updating functionality of the specified cluster after the Cluster-Aware Updating (CAU) operation is complete.
Table 1. Additional resources (continued) Document Description Availability Microsoft Windows Admin Center documentation For more information about using Microsoft Windows Admin Center. https://www.microsoft.
2 Getting started with OpenManage Integration with Microsoft Windows Admin Center Before you launch Dell EMC OpenManage Integration extension in Windows Admin Center, ensure that you have: • Logged in to Windows Admin Center as a gateway administrator. After installing the OpenManage Integration with Microsoft Windows Admin Center (OMIMSWAC), perform the following actions to launch the extension: 1. In the upper left corner of Windows Admin Center, select: • For 1910.
3 Ports required by Dell EMC OpenManage Integration with Microsoft Windows Admin Center Table 2.
4 Manage Dell EMC PowerEdge Servers Prerequisites: • • • You must be logged in to Microsoft Windows Admin Center as a Gateway Administrator. You must have installed the Dell EMC OpenManage Integration with Microsoft Windows Admin Center (OMIMSWAC) extension. For more information about the installation procedure, see the Dell EMC OpenManage Integration with Microsoft Windows Admin Center Installation Guide. Server connections are added in Microsoft Windows Admin Center.
Health status—Supported target node components Health status of the following target node components is displayed: • • • • • • • • • • • CPUs Accelerators Memory Storage Controllers Storage Enclosures Physical Disks iDRAC Power Supplies Fans Voltages Temperatures NOTE: Health status information is available for Accelerators in YX4X models of PowerEdge servers and above with iDRAC version 4.00.00.00 or newer. NOTE: Intel DIMM memory is identified as IntelPersistent with an icon.
○ Disks associated to Boot Optimized Storage Subsystem (BOSS) cards. ○ Devices with iDRAC firmware version less than 3.30.30.30. Update the iDRAC firmware to the latest version to enable blink and unblink operations. NOTE: ○ When the blink or unblink operation is running, Refresh button to load the latest health and hardware inventory information is disabled. Also, when the health and hardware inventory is being loaded in OMIMSWAC, blink and unblink operations is disabled.
5 Manage Failover Clusters and Azure Stack HCI Prerequisites: • • • • You are logged in to Microsoft Windows Admin Center as a Gateway Administrator. You must have installed the Dell EMC OpenManage Integration with Microsoft Windows Admin Center (OMIMSWAC) extension. For more information about the installation procedure, see the Dell EMC OpenManage Integration with Microsoft Windows Admin Center Installation Guide.
Health status—Supported target node components in Failover Clusters and Azure Stack HCI On the Cluster - Azure Stack HCI page, select the Health tab to view the overall health status of the Failover or HCI cluster and the health status of the following target node components of the nodes in Failover Cluster or Azure Stack HCI. Selecting critical or warning section in the overall health status doughnut chart displays corresponding nodes and the components in the critical or warning state respectively.
To view the additional properties of a disk, select the disk, and then click Advanced Properties. To view the associated storage controller, click the storage controller link under Advanced Properties. The associated storage controller is displayed in the Storage Controllers tab. If physical disks are attached to the CPU, then the storage controller link will not be available under Advanced Properties.
6 View iDRAC details of the PowerEdge servers and nodes of HCI and Failover clusters To view the following iDRAC details of the target node, select Server Manager or Cluster Manager from the upper left corner of Microsoft Windows Admin Center, and then select a server or cluster connection from the list. In the left pane, under EXTENSIONS, click Dell EMC OpenManage Integration and navigate to the iDRAC tab. NOTE: For failover and hyper-converged clusters, expand the nodes to view the following details.
7 Update PowerEdge servers and nodes of HCI and Failover clusters OpenManage Integration with Microsoft Windows Admin Center (OMIMSWAC) allows you to generate compliance details and update components, such as BIOS, driver, firmware, and/or system management applications of target nodes and nodes in an HCI and failover clusters. You can use either an online or offline catalog to generate compliance details and update components. In OMIMSWAC, click Update. The update window is displayed.
DSU is used to apply the Dell update packages to target nodes. 2. Enter the share location where the IC utility is placed. The IC utility is used to collect the hardware inventory information from target nodes. 3. Enter the user credentials to access the share location. NOTE: When OMIMSWAC is uninstalled, the data present in the Settings page is not deleted. If the OMIMSWAC is later reinstalled, previously configured data in the Settings page is still available to it.
• 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.
2. Enter the CIFS share path where catalog files are placed and the user credentials to access the CIFS share path, and then select Next: Compliance details:. The catalog files can be generated by using the Dell EMC Repository Manager (DRM) application. Ensure that in the shared catalog repository all the required Dell Update Packages (DUP) are available for the target node. If a new catalog path is provided, the previous path that was used to compute the update compliance may not be available.
Compliance Type Specifies whether the component is Upgradable, Downgradable, or Same. • • • Upgradable: Component can be upgraded from the current version. Downgradable: Component can be downgraded from the current version. Same: Component current verison is same as the baseline version. 1. By default, all the non-compliant upgradable components are selected. Clear the selected components or select the non-compliant downgradable components that you want to update.
• • • • • • • Software and hardware requirements listed in the compatibility matrix of the Installation Guide are met. 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 administrator credentials. And ensure that the user is part of the local user group of gateway administrators.
You will be directed to the compliance report generated in the Compliance Details window. For more details about compliance report, see View compliance report. Generating compliance report using offline catalog OMIMSWAC with or without Internet access allows you to select the Offline - Dell EMC Repository Manager Catalog to generate compliance report. Before you generate the latest compliance report of a cluster, ensure the followings.
For example: SerialATA_Firmware_6FGD4_WN64_E012_A00 Compliance Specifies compliance type whether compliant or non-compliant. • • Criticality Specifies whether compliance is urgent, recommended, or optional. • • • Current Version Compliant - Target nodes in this category have the same versions of BIOS, drivers, firmware, and system management application as that of the imported catalog.
Step 3: Updating—Target node components in Failover Clusters and Azure Stack HCI After generating the compliance report in the Compliance Details tab and confirming the components selection in the Summary tab, proceed to update the target node components in Failover Clusters and Azure Stack HCI as follows: 1.
8 Troubleshooting Topics: • • • • • • • • • • Availability of OMIMSWAC extension logs Availability of update operation logs Unable to copy the required files to the target node to fetch inventory information. Unable to fetch the health and hardware inventory from iDRAC. Unable to complete or select the disks for the blink or unblink operations. Licensing status is Unknown or Non-licensed Job failed while downloading the required components for the server and cluster-aware updating operations.
Unable to copy the required files to the target node to fetch inventory information. Ensure that: • • Target node is not in the reboot state and is powered on. Firewall is not blocking communication through SMB port 445. For more information, see prepare your environment for Windows Admin Center. Unable to fetch the health and hardware inventory from iDRAC.
2. Ensure that Redfish service is enabled. 3. Disable OS to iDRAC Pass-through and then enable it. For more information about enabling or disabling OS to iDRAC Pass-through, see iDRAC user guide. Availability of licensing logs The license related logs are available at the following path and can be found by searching DellLicenseCollection in the Cleanup file. • • Gateway system: \ServiceProfiles\NetworkService\AppData\Local\Temp\generated \logs\CleanupXXXXXXXXXXXXXX.
• File copying works between the gateway system and the target node. To check this: 1. Create a session based on target node credential by executing the following PowerShell command: $SecurePassword = convertto-securestring -asplaintext -force $credential = New-Object System.Management.Automation.PSCredential -ArgumentList , $SecurePassword $session = New-PSSession -ComputerName -Credential $credential -ErrorAction SilentlyContinue 2.
Component showing non-compliant after update After update, you may see components showing as non-compliant. Resolution: In this case, check the cleanup logs having the DSU logs to see if there is any ERROR for the component. If there is any prerequisite that is required for the component before update, follow the prerequisite and then rerun the update.
• • Run the update manually in the target node by downloading from the path specified in \Dell \UpdatePackage\log\ in the DUP log. Example for a network firmware is https://downloads.dell.com/ FOLDER06091050M/1/Network_Firmware_TWFF6_WN64_16.26.60.00.EXE. Ensure that the selected DUP is supported on the selected operating system and platform by searching the component name in the Dell Support site. Dell support site URL: https://www.dell.
9 Identifying the generation of your Dell EMC PowerEdge server To cover a range of server models, the PowerEdge servers are now be referred to using the generic naming convention and not their generation. This topic explains how to identify the generation of a PowerEdge server that are referred to using the generic naming convention. Example: The R740 server model is a rack, two processor system from the 14th generation of servers with Intel processors.
10 Contacting Dell EMC Dell EMC provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell EMC product catalog. To contact Dell EMC for sales, technical support, or customer service issues: 1. Go to Dell.com/support. 2.
A Glossary The following table defines or identifies abbreviations and acronyms used in this document. Table 4.
Table 4. Glossary (continued) Abbreviations/ Acronyms Definition Offline - Dell EMC Repository Manager Catalog Recommended when the DRM repositories are available in a shared location and is applicable for all managed devices by OMIMSWAC in data centers with no Internet connectivity.
B Appendix SAS-RAID_Driver While performing update compliance operation for SAS-RAID_Driver, ensure that SATA controller and NVMe PCIe SSDs are set to RAID mode. To configure RAID mode: 1. When the Dell Power-On Self-Test (POST) screen is displayed, press F2. Dell PowerEdge System Setup window is displayed. • • Under System BIOS setting , configure RAID mode in SATA settings > Embedded SATA. Under System BIOS setting , configure RAID mode in NVMe settings > NVMe mode.
