The errors in vCenter related to VUM are now resolved. A reinstall of VUM did not resolve it, as the VUM plug-in was actually the source of the error.
The domain id provisioned for connecting to the database (SQL Server 2005) was applied to the VMware Update Manager Service on VCS01 (the id is already used for the VMware vCenter Server Service). Previously, the VUM service was using the local system account for VCS01. This is legacy from the reinstall of vCenter last week.
After applying the id and restarting the service, the VUM plug-in could be re-enabled and vSphere fixes were being updated in VUM. A maintenance cycle will be scheduled for early next week to play around more with VUM. vSphere 4.1 is still on the list.
No comments:
Post a Comment