First of all I want to apologize that vCenter failover feature requires so many configuration steps, but there is no other way of creating such a complicated recovery action scenario without making sure SCOM has all necessary permissions for configured RunAs accounts.
This is a known issue and we have it documented in multiple places, in documentation (Release Notes
) and in the Product Knowledge:Causes
If the default action account for the Ops Mgr agent on the Veeam Virtualization Extensions Service machine does not have access to the Veeam VEShell (PowerShell interface), you may see error messages such as:
• '[User ID]' account unable to access the Veeam Virtualization Extensions Service.
This error could occur for any agent action account that cannot access Veeam VEShell, including LocalSystem.Resolutions
To fix the permissions issue detailed in Causes above, the account specified as default Action Account should be added to the 'Veeam Virtualization Extensions for VMware Users' local group on the server running the Veeam Virtualization Extensions Service. Alternatively, if LocalSystem is the Action Account, and adding LocalSystem to the group is not desired, then change the agent Action Account to be a domain user account, and add this account to the local group. Note that this account should also be an Administrator of the local server.
Once Action Account is in the group - the script for vCenter connection failover should work properly.
Feel free to ask other questions regarding this new vCenter connection failover functionality.
I would also highly appreciate if you can provide us with your support ticket ID.