Users Guide

Resolution: In Administration Console, manually copy the path in the Default Update Repository field to the Update
Repository Path field.
Why firmware update for 30 hosts at cluster level fails
VMware recommends you to build clusters with identical server hardware. For firmware update at a cluster level with the
number of hosts that is near the maximum limit for a cluster (as recommended by VMware) or composed of different models of
Dell servers, use vSphere web client.
Why warranty and inventory schedule for all vCenters is not
applying when selected from the job queue page?
Navigate to Dell Home > Monitor > Job Queue > Warranty/Inventory History > Schedule. Select a vCenter and select
the modify schedule button. When a dialog is displayed, you can view a check box with the Apply to All Registered vCenters
message. When you select the check box and press Apply, the setting is applied to a particular vCenter that you had initially
selected and not all vCenters. The Apply to All Registered vCenters is not applicable when warranty or inventory schedule is
modified from the Job Queue page.
Resolution: Use the modify warranty or inventory schedule from the job queue only to modify the selected vCenter.
Versions Affected: 2.2 and later
What should I do when a web communication error in the vCenter
web client appears after changing the DNS settings in OMIVV?
If you see any kind of web communication error in the vCenter web 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.
Why does the settings page fail to load, if I navigate away and
again go back to the settings page?
For vSphere v5.5, in web client, if you navigate away and go back to the Settings page, the page might fail to load and the
spinner continues to spin. The failure to load is a refresh issue and the page is not refreshing correctly.
Resolution: Click the global refresh and the screen refreshes correctly.
Versions Affected: 2.2 and 3.0
Why “Task cannot be scheduled for the time in the past” error in
inventory schedule/warranty schedule page of Initial Configuration
Wizard appear?
In web client, the error “Task cannot be scheduled for the time in the past” appears:
● if you select ‘All registered vCenters’ in the Initial Configuration wizard, and there are some vCenters with no hosts.
● when vCenters where some have inventory or warranty tasks already scheduled.
● when some vCenters with no inventory or warranty schedule set yet.
Resolution: Run the setting of inventory and warranty schedule separately again from the Settings page for the vCenters.
Versions Affected: 2.2 and later
Troubleshooting
119