Release Notes

Description: Navigating away from the firmware update page by selecting another host in the
datacenter tree causes the update to fail. The update fails by not entering Maintenance mode
and the reboot tasks will fail to initiate.
Resolution/Workaround: You must close the wizard before selecting any another host in the
inventory.
Version Affected: All
Issue 24: The Service Tag is not displayed during a firmware update.
Description: In the firmware inventory and on the Select Update Bundles tab, the Service Tag
information is not displayed for Dell PowerEdge 11th generation servers. This information is not
displayed if VMware vCenter does not provide the Service Tag.
Resolution/Workaround: You can view the Service Tag information on the Host Overview page
from where you launched the firmware update.
Version Affected: All
Issue 25: ESX or ESXi deployment fails on servers having a PERC S300 boot controller.
Description: Deployments of OpenManage Integration using different ESX or ESXi versions on
Dell PowerEdge servers with the PERC S300 boot controller failed. The Dell Customized ESX or
ESXi operating systems do not contain the driver for the PERC S300 boot controller, which
causes the boot controller or HDD not to be recognized during operating system installation.
Resolution/Workaround: Servers with PERC S300 boot controllers are not supported for
OpenManage Integration deployments.
Version Affected: All
Issue 26: The RAID topology does not support a dedicated hot-spare in the reference topology and also
does not support a dedicated hot-spare while applying a hardware profile.
Description: Raid Topology does not support a dedicated hot-spare in the reference topology
and also does not support dedicated hot-spare while applying hardware profile.
Resolution/Workaround: If you need a dedicated hot-spare in reference topology, set the RAID
outside of the OpenManage Integration.
Version Affected: All
Issue 27: Associated Connection Profile is not displayed in the host compliance page when inventory is
not able to get iDRAC IP for the host.
Description: If the iDRAC IP is not retrieved because of non-responsive iDRAC, the inventory
fails and host to be associated with the connection profile is not displayed on the host
compliance page.