Although everything is set up according to vCenter Connection Failover manual, the script fails to run. As a result, the following event appears in Operations Manager Event Log on Veeam Virtualizations Extension Server (VES)
"vCenterFailover.ps1 : Error: Cannot open connection. Reason: User ''NT AUTHORITY\SYSTEM' is not allowed to access the Veeam Virtualization Extensions." with id: 995
The error also triggers Veeam VMware Collector: vCenter connection failover errors and warnings Event Rule to generate a message in SCOM console.
The script is executed under SCOM Default Action Account or under account defined in Default Action Account profile for VES server.
If you use Local System account as an Action Account in most cases adding "NT AUTHORITY\SYSTEM" to Veeam Virtualization Extensions for VMware Users local group doesn't work.
Please use a domain account as SCOM Action Account for Veeam Virtualizations Extension Server.
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.