The behavior described here can be observed in the following configuration:
- multiple installations of Veeam Agent for Microsoft Windows (VAW) are targeted at a Veeam Backup and Replication (VBR) repository within the same domain; - all VAW-processed computers are added to an AD computer group; - the mentioned group is used to manage Agent Backup Permissions to access the repository.
This configuration works fine for all VAW installation except the one on the VBR server.
During the authentication on the same machine, Kerberos authentication is not used, thus making the repository unavailable for the local installation of VAW.
A group which contains NT AUTHORITY\SYSTEM account should be added to the Agents Backup Permissions.
By default, the BUILTIN\Administrators group contains the Local System account.
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.
Spelling error in text
Your feedback has been received and will be reviewed.