Users Guide

Table Of Contents
I get an exception whenever I click finish after editing a connection
profile through Web Client. Why?
This happens when the vCenter server is registered to the appliance through IP instead of FQDN. The connection profile can
be edited through the Desktop client. Re-registering the vCenter server to the same appliance will not solve this. A new setup
registered with FQDN is required.
I am unable to see the connection profiles to which a host belongs
to when I create\edit a connection profile in web GUI. Why?
This happens when the vCenter server is registered to the appliance through IP instead of FQDN. Re-registering the vCenter
server to the same appliance will not solve this. A new setup registered with FQDN is required.
On editing a Connection profile the select host window in the Web
UI is blank. Why?
This happens when the vCenter server is registered to the appliance through IP instead of FQDN. Re-registering the vCenter
server to the same appliance will not solve this . A new setup registered with FQDN is required.
How Come I See An Error Message Displayed After Clicking The
Firmware Link?
If you have a slow network speed (9600BPS), you may get a Communication Error Message. This error message may display
when you click the Firmware link in the vSphere Client for the OpenManage Integration for VMware vCenter. It happens when
the connection times out while trying to obtain the Software Inventory list. Microsoft Internet Explorer initiates this timeout. For
Microsoft Internet Explorer versions 9/10, the default Receive Time out value is set to 10 seconds. Fix this issue by using the
following steps.
Figure 1. Firmware link communication error
1. Open Microsoft Registry Editor (Regedit).
2. Navigate to the following location:
KHEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
3. Add a DWORD value for ReceiveTimeout.
4. Set the value to 30 seconds (30000) [This value may need to be a higher value in your environment].
5. Exit Regedit.
6. Restart Internet Explorer.
118
Troubleshooting