Release Notes

Fixes
This release includes improvements and bug fixes, including the following previously reported Known Issues that are now
resolved:
● Multiple ports of same NIC is listed for firmware update
● OS Driver Pack DUP update fails
● DRS Check during firmware update
● Connection profiles missing
● vCenter Restart during Proactive HA registration
● Security Updates
● Granular privilege for iDRAC Lockdown Mode
Known Issues and Resolutions
● Issue 1: iDRAC might not send an event when your system reboots.
Description: Sometimes the iDRAC might not send an event when your system reboots. In this case, OMIVV sends latest
health update notification by polling mechanism and you will receive the latest health update within an hour.
Version affected: 4.0 and later
● Issue 2: The Export All button fails to export to .CSV file in the Google chrome.
Description: After registering a vCenter server, if you add a host and create a connection profile, and then view the
inventory details of the host, the Export All button returns a failure. The Export All button does not export the information
to a .CSV file.
NOTE:
In all versions of the Google chrome browser, the Export All button does not export the information to a .CSV file in
Incognito mode.
Version affected: 4.0
Resolution/Workaround: To export information to a .CSV file by using the Export All button in the Google chrome, disable
the Incognito mode in chrome browser.
● Issue 3: iDRAC license type and description are displayed incorrectly for non-compliant vSphere hosts.
Description: If a host is noncomplaint when CSIOR is disabled or has not been run, the iDRAC license information is displayed
incorrectly although valid iDRAC license is available. Hence, you can view the host in vSphere hosts list, but when you click
the host for details, the information in iDRAC License Type is displayed as empty and iDRAC License Description is
displayed as "Your license needs to be upgraded".
Version affected: 4.0
Resolution/Workaround: None
● Issue 4: Although deployment job fails due to inaccessible file share, the status is displayed as “Cancel”.
Description: When you create a hypervisor profile with invalid credentials such as, invalid credentials for CIFS share, and
select the same hypervisor profile for deployment, the deployment task fails. However, the status displayed in the Job
Queue page is Cancel instead of Failed.
Version affected: 3.0 and later
Resolution/Workaround: None
● Issue 5: Dell icon is not displayed after unregistering vCenter from an earlier OMIVV version and then registering same
vCenter with a later OMIVV version.
Description: If you unregister an earlier OMIVV version with vCenter server, and then register a later OMIVV version with the
same vCenter server, there is an entry in the vsphere-client-serenity folder, which is old data from the earlier OMIVV
version. Hence, the Dell icon is not displayed after registering the later OMIVV version as old data specific to the earlier
OMIVV version exists in the vsphere-client-serenity folder of the vCenter appliance.
Version affected: All
3