Release Notes

Known issues
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 receive the latest health update within an hour.
Version affected: 4.0 and later
● Issue 2: 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 and later
Resolution/Workaround: Perform any one of the following:
1. Fix CSIOR compliance and run the inventory.
2. Log in to iDRAC to get the license information.
● Issue 3: Although deployment job fails due to inaccessible file share, the status is displayed as “Cancel.”
Description: When you create an ISO profile with invalid credentials such as, invalid credentials for CIFS share, and select
the same ISO profile for deployment, the deployment task fails. However, the status displayed in the Jobs page as Cancel
instead of Failed.
Version affected: 3.0 and later
Resolution/Workaround: None
● Issue 4: Dell EMC 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 EMC 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
Resolution/Workaround: Perform the following steps:
1. Restart vSphere Client on the vCenter server.
2. If the issue persists:
○ For VMware vCenter, go to /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity
and for Windows vCenter, go to C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-
packages\vsphere-client-serenity folder in the vCenter appliance and see if the old data exists, such as:
com.dell.plugin.OpenManage_Integration_for_VMware_vCenter_WebClient-X.0.0.xxx.
○ Manually deleted the folder corresponding to the earlier OMIVV version
○ Restart vSphere Client services for vSphere Client (HTML-5).
● Issue 5: The OpenManage Integration icon is not displayed after backup and restore from an earlier OMIVV version to a
later OMIVV version.
Description: The OpenManage Integration icon is not displayed after restoring an earlier OMIVV version appliance database
to a later OMIVV version appliance.
Version affected: 3.0 and later
6
Known issues 9