Operational Defect Database

BugZero found this defect 3843 days ago.

Veeam | kb1829

vCenter Connection Failover Requirements for SCOM Action Account

Last update date:

11/19/2020

Affected products:

Veeam Management Pack for Microsoft System Center

Affected releases:

8.0

Fixed releases:

No fixed releases provided.

Description:

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


Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Solved

Learn More

Search:

...