Challenge
Although everything is set up according to the vCenter Connection Failover manual, the script fails. As a result, the following event appears in the Operations Manager Event Log on Veeam Virtualizations Extension Server (VES) with id: 995.
vCenterFailover.ps1 : Error: Cannot open connection. Reason: User ''NT AUTHORITY\SYSTEM' is not allowed to access the Veeam Virtualization Extensions.
The error also triggers Veeam VMware Collector: vCenter connection failover errors and warnings Event Rule to generate a message in the SCOM console.
Cause
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.
Solution
Please use a domain account as SCOM Action Account for Veeam Virtualizations Extension Server.
