Users Guide
Table Of Contents
- Dell EMC OpenManage Integration Version 2.0 with Microsoft Windows Admin Center User’s Guide
- Contents
- Overview of OpenManage Integration with Microsoft Windows Admin Center
- Getting started with OpenManage Integration with Microsoft Windows Admin Center
- Ports required by Dell EMC OpenManage Integration with Microsoft Windows Admin Center
- Manage Dell EMC PowerEdge Servers
- Manage Failover clusters, Azure Stack HCI, and Windows Server HCI clusters
- View iDRAC details of the PowerEdge servers and nodes of HCI and Failover clusters
- Update PowerEdge servers and nodes of Windows Server HCI, Azure Stack HCI, and Failover clusters using OpenManage Integration extension
- Integrated deploy and update of Azure Stack HCI clusters
- Full Stack Cluster-Aware Updating for Azure Stack HCI clusters using OpenManage Integration snap-in
- Troubleshooting
- Identifying the generation of your Dell EMC PowerEdge server
- Contacting Dell EMC
- Glossary
- Appendix
● Firewall is not blocking communication through SMB port 445. For more information, see prepare your environment for
Windows Admin Center.
● The USB NIC adapter is not disabled on the target node operating system.
Unable to fetch the health and hardware inventory from iDRAC
To fetch the health and hardware inventory information from iDRAC, ensure that:
● YX3X and YX2X models of PowerEdge servers are updated with latest iDRAC version of 2.60.60.60 or later.
● YX4X models of PowerEdge Servers are updated with latest iDRAC version of 3.30.30.30 or later.
● For management of PowerEdge servers, OMIMSWAC uses an internal operating system to iDRAC Pass-through interface.
By default, iDRAC is reachable using the IP address 169.254.0.1/<Subnet> or 169.254.1.1/<Subnet>. However, if the host has
another network interface in the same subnet (for example, when tool such as VMFleet is installed), OMIMSWAC might not
be able to communicate to the iDRAC from the host operating system.
To resolve the conflict, log in to iDRAC and change the USB NIC IP address under the operating system to iDRAC
passthrough section. For more information about assigning this IP address, see the iDRAC documentation on the support
site.
● For management of Clusters, all the cluster nodes are reachable using IP address, Hostname, and Fully Qualified Domain
Name (FQDN) before managing the cluster with OMIMSWAC.
● If the Redfish service is disabled, enable the Redfish service by using iDRAC UI. For more information, see the iDRAC
documentation on Dell EMC support site.
● User slots are available on iDRAC to create new users.
Health and hardware inventory of YX2X, YX3X, and YX4X models of
PowerEdge servers not displayed
● Ensure that YX3X and YX2X models of PowerEdge servers are updated with latest iDRAC version of 2.60.60.60 or later.
● Ensure that YX4X models of PowerEdge Servers are updated with latest iDRAC version of 3.30.30.30 or later.
Overall health status shows warning or critical while health status of node
components shows healthy
The overall health status of PowerEdge servers, failover clusters, and HCI clusters might be displayed as critical or warning even
if the components of the nodes displayed on the Windows Admin Center are healthy. Because the health status of physical disks
that are attached to embedded SATA controller may be displayed as Unknown as iDRAC is unable to get the health information
for these disks.
For more details on the components in critical health state, go to the respective iDRAC console.
Unable to create users on target iDRAC device
If the lockdown mode is enabled on YX4X model of PowerEdge Servers and above, inventory of health, hardware, and iDRAC
fails with the error: “Unable to create users on target iDRAC device.”
Resolution: Disable the lockdown mode on the target node managed by Dell EMC OpenManage Integration.
Unable to initialize the OMIMSWAC extension.
Retrieving inventory from servers and cluster nodes may fail with the error: Unable to initialize the OMIMSWAC extension.
Resolution: Ensure the IPMI driver is installed, and the IPMI service is running on the target node. For more information on the
requirement and solution, see Dell information center.
Troubleshooting
39