- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We had similar problems - the 3 fixes were:-
- KB2119768 - add db_owner role to msdb (we thought this had been fixed with the 'VMW' schema and admin roles)
- KB2114754 - add permissions to the vCenter_database_user (** NOTE - the upgrade script to prepare the MSSQL database grants these permissions to [vpxuser] and we have a different user
- KB2119606 - add administraor@vsphere.local to DC Admins group
Hopefully this may help some others.