IcyAero wrote:When assigning permissions to a backup repository to a single user (lets say Test User) via Active Directory, Veeam Backup & Replication formats the username to DOMAIN\test.user - although the actual account name is firstname.lastname@example.org and pre-Windows 2000 account name is DOMAIN\tuser. Obviously this leads to an error message of "Account does not exist".
IcyAero wrote:I believe in this case the client fetches the Windows credentials (ideal situation), but fails to connect to the server with said credentials.
foggy wrote:Hi Eero, Veeam B&R requires account name in DOMAIN\USER format, it is mentioned in the wizard when you're adding Windows server to Veeam B&R console.
foggy wrote:In this case it connects to Veeam B&R using computer account of the server where Veeam Endpoint is installed, so user credentials do not play any role here. If you give the group containing all accounts of Endpoint computers permissions to repository, you will be able to connect without specifying credentials.
IcyAero wrote:My understanding is also that VBR requires the format to be DOMAIN\username. This works like intended when adding Security Groups or Computer objects to the list but not for individual Users. With individual users, VBR formats the name into DOMAIN\firstname.surname instead of DOMAIN\user with mail enabled user accounts. This does not happen when adding a service-kind user account.
IcyAero wrote:Also when changing account passwords, users most often forget to change them to other applications unless prompted for it - which at this time the Endpoint Backup does not do.
foggy wrote:Actually the required format is DOMAIN\<samAccountname>, while some of the accounts can have samAccountname = firstname.surname and others samAccountname = fsurname (or anything else).
foggy wrote:Using computer accounts to assign permissions will allow to prevent such issues.
Users browsing this forum: Bing [Bot], Google [Bot] and 15 guests