Users Guide

In Administration Console, Update Repository Path is not
set to default path after I reset appliance to factory
settings
After you reset the appliance, go to the Administration Console, and then click APPLIANCE MANAGEMENT in the left pane. In the
Appliance Settings page, the Update Repository Path is not changed to the default path.
Resolution: In Administration Console, manually copy the path in the Default Update Repository field to the Update Repository
Path field.
What should I do when a web communication error in the
vCenter HTML-5 Client opens after changing the DNS
settings in OMIVV
If you see any kind of web communication error in the vCenter HTML-5 Client while doing any OMIVV-related tasks after changing the
DNS settings, do either of the following:
• Clear the browser cache.
• Log out and then log in from web client.
Installation date be displays as 12-31-1969 for some of the
firmware on the firmware page
In web client, the installation date be displays as 12/31/1969 for some firmware items on the firmware page for a host. If the firmware
installation date is not available, the old date is displayed.
Resolution: If you see this old date for any firmware component, consider that the installation date is not available for it.
Versions Affected: 2.2 and later
I am not seeing OpenManage Integration icon in HTML-5
Client even if registration of plug-in to vCenter was
successful
OpenManage Integration icon is not displayed in the vSphere client unless the vSphere client services are restarted. When you register the
OpenManage Integration for VMware vCenter appliance, the appliance is registered with the vSphere client. If you unregister the
appliance and then either re-register the same version or register a new version of the appliance, it successfully registers, but the OMIVV
icon may not be display in the vSphere Client. This is due to a caching issue from VMware. To clear the issue, ensure that you restart the
Sphere Client service on the vCenter Server. Then the plug-in is displayed in the UI.
Resolution: Restart the vSphere client services on the vCenter server.
Version Affected: 2.2 and later
Why is DNS configuration settings restored to original
settings after appliance reboot if appliance IP and DNS
settings are overwritten with DHCP values
There is a known defect where statically assigned DNS settings are replaced by values from DHCP. This can happen when DHCP is used
to obtain IP settings, and DNS values are assigned statically. When the DHCP lease is renewed or the appliance is restarted, the statically
assigned DNS settings are removed.
Resolution: Statically assign IP settings when the DNS server settings are different from DHCP.
Frequently Asked Questions-FAQ
133