Users Guide

Why am I not seeing the OpenManage Integration Icon on the Web
Client even if the registration of the plug-in to the vCenter was
successful?
OpenManage Integration icon is not displayed on the Web client unless the vCenter Web Client services are restarted or the
Box is rebooted. When a user registers the OpenManage Integration for VMware vCenter appliance, it registers with both the
Desktop client and the Web client. If a user unregisters the appliance and then either reregisters the same version or registers
a new version of the appliance, it will successfully register with both clients, but the Dell icon may not appear in the Web
Client. This is due to a caching issue from VMware. To clear the issue, a user needs to restart the Web Client Service on the
vCenter Server. Only then will the plug-in appear in the UI.
Resolution: Restart the Web Client Service on the vCenter Server.
Version Affected: 2.2 and later
Even if my repository has bundles for selected 11G system, why
is firmware update showing that I have no bundles for Firmware
Update?
When I added a host to the connection profile in lockdown mode, the inventory kicked off but failed stating that “No Remote
Access Controller was found or Inventory is not supported on this host.” Inventory is supposed to work for a host in lockdown
mode, right?
If you put the host in lockdown mode or remove a host from lockdown mode, you must wait 30–minutes before performing the
next operation. If you use a 11G host for firmware update, the firmware update wizard will not show any bundles even if the
repository provided has bundles for that system. This occurs because the 11G host might have not been configured for OMSA
to send traps to OpenManage Integration.
Resolution: Ensure that the host is compliant using the host Compliance screen of OpenManage Integration desktop client. If it
is not compliant, use the fix Host Compliance to get it compliant.
Version Affected: 2.2 and later
On running a warranty retrieval job, the warranty job status is not
listed in the Warranty Job Queue page
If your network needs proxy details to connect to the internet and the proxy is not set on the OMIVV appliance, the warranty
retrieval job fails and the job is not listed under warranty job queue.
Resolution: Set the proxy details and trigger the warranty job again.
Version Affected: All
Why is the DNS configuration settings restored to original settings
after appliance reboot if using DHCP for appliance IP and DNS
settings overwritten
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 will be different from DHCP.
Version Affected: All
116
Troubleshooting