- Veeam Support Knowledge Base
- vCenter Connection Failover Requirements for SCOM Action Account
vCenter Connection Failover Requirements for SCOM Action Account
| KB ID: | 1829 |
| Product: | Veeam Management Pack | 6.0 | 6.5 | 7.0 | 8.0 | 9.0 | 9a | 13 |
| Published: | 2013-11-11 |
| Last Modified: | 2024-12-26 |
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
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
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
