https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxODI5IiwiaGFzaCI6IjRkN2M1ZTU5LWVlYzMtNDY3Yy1iZDdlLTNmODYwMWQ2ZTBlZSJ9
1-800-691-1991 | 9am - 8pm ET
EN

vCenter Connection Failover Requirements for SCOM Action Account

Challenge

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.

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.

More information


KB ID:
1829
Product:
Veeam Management Pack for Microsoft System Center
Version:
6.5
Published:
2013-11-11
Last Modified:
2020-08-28
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later