Release Notes
While installing OMIMSWAC by using local path or network path, multiple instances of OMIMSWAC extension might be listed under
Available and Installed Extensions when more than one .nupkg packages are available in the specified folder path, or the .nupkg packages
are available in root or subfolders in addition to the folder path provided under Feeds > Add package source.
Workaround
Ensure that a single .nupkg package is available in the root or subfolders under Feeds > Add package source.
Issue 5
Description
When you navigate out of OpenManage Integration to other tools under HCI or Failover solutions and navigate back to OpenManage
Integration, the following error is displayed: "Enabling CredSSP Delegation".
Workaround
Ignore the error because the functionality of OpenManage Integration and Windows Admin Center is not blocked.
Issue 6
Description
If the lockdown mode is enabled on YX4X models of Dell EMC PowerEdge servers, inventory of health, hardware, and iDRAC fails with
error: “Unable to create users on target iDRAC device.”
Workaround
Disable the lockdown mode on the target node managed by Dell EMC OpenManage Integration.
Issue 7
Description
The update compliance report might not generated for the cluster nodes.
Workaround
Ensure that the cluster service is running on the cluster node by using the Get -ClusterService PowerShell command, and also
ensure that the cluster node is not rebooting or in the powered-off state.
Issue 8
Description
The attribute values of hardware inventory information for storage enclosure components might be empty because the information is not
available on the target iDRAC.
Issue 9
Description
The overall health status of the PowerEdge servers and HCI cluster might be displayed as critical or warning even though the components
of the nodes displayed on the Windows Admin Center are healthy. The health status of physical disks attached to embedded SATA
controller may be displayed as Unknown because iDRAC is unable to get the health information for these disks.
Issue 10
Description
The update compliance may intermittently and partially succeed for server and cluster nodes.
Workaround
Rerun the compliance with the same input details.
8
Known issues