Release Notes

● Issue 21: I see a web communication error in the vSphere Client after changing the DNS settings in OpenManage Integration
for VMware vCenter.
Description: If you see any kind of web communication error in the vSphere Client while doing any OMIVV-related tasks after
changing the DNS settings, clear the browser cache or log out and log in from the vSphere Client.
Version affected: 2.x and later
Resolution/Workaround: Clear the browser cache or log out and log in from the vSphere Client.
● Issue 22: OMIVV RPM Upgrade fails when Proxy is configured with Domain user authentication.
Description: If OMIVV appliance is configured with proxy to reach the Internet and proxy is authenticated using NTLM
authentication, then the RPM update fails due to the issues in the underlying yum tool.
Version Affected: OMIVV 4.0 and later
Resolution/Workaround: Do back up and restore to update the OMIVV appliance.
● Issue 23: Unable to apply system profile that has PCIe card in the FX chassis.
Description: The OS deployment fails on a target server if the source server has PCIe card information when using an FX
chassis. The System profiles on the source server have different fc.chassislot ID than the one on the target server.
OMIVV tries to deploy the same fc.chassislot ID on the target server but fails. The System profiles searches for
exact instance( FQDD) while applying the profile, which works successfully on rack servers (identical), but may have few
restrictions in modular servers. For example, in FC640, the System profiles that are created from one modular server cannot
be applied on other modular servers in the same FX chassis because of NIC level restrictions.
Version Affected: OMIVV 4.1 and later
Resolution/Workaround: System profile that is taken from an FC640 server in slot 1 of a FX2s chassis can only be applied on
another FC640 server residing in the slot 1 of another FX2s chassis.
● Issue 24: The first inventory (immediately after creating a host credential profile) may fail in ESXi 6.5 and later version
where the WBEM enablement is necessary.
Resolution: Trigger the inventory again from Jobs.
● Issue 25: After backup and restore from an earlier OMIVV version to a later OMIVV version, the following issues may be
observed:
○ The Dell EMC logo is not displayed at vCenter.
○ The 2000000 error
○ The 3001 error
Resolution:
￭ Restart vSphere Web Client on the vCenter server.
￭ 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
● Issue 26: Proactive HA-related features are not functioning as expected after modifying the vCenter credentials.
Description: If the vCenter credentials are modified by using the OMIVV portal after registering the OMIVV to a vCenter, the
Proactive HA-related features will not function as expected.
Resolution: If you are using the Proactive HA feature along with OMIVV, do not modify the registered user credentials. If the
credentials require modification, unregister and register OMIVV appliance to vCenter with new username.
Version Affected: 4.3 and later
● Issue 27: When upgrading or downgrading some iDRAC firmware versions using OMIVV, even when the firmware update is
successful, OMIVV may indicate that the job is failed.
Description: During firmware update, when you downgrade or upgrade the iDRAC versions such as 3.20.20.20, 3.21.21.21,
and 3.21.21.22, the job status is indicated as failed even when the job was successfully run.
Resolution: Refresh the inventory after the job failure and rerun the job for other components.
Version Affected: 4.3 and later
12
Known issues