Skip to main content
Question

VEEAM Backup User Windows Server 2019 Admin Rights not enough

K

Hi,

To save our Windows 2019 Server we still use the local administrator account.

Due to restriction template from security reason, we want to get away and use another login user.

I created a local user e.g. veeambackup. I put this into the local administrator group.

 

At my veeam backup server I use the credentials of the local veeam backup user of the windows 2019 server. It is not working. So I still use the local administrator user of the windows 2019 server and this works fine.

 

Can anyone give me a hand to solve this?

 

Best regards,

Heinz

3 comments

lukas.k
Forum|alt.badge.img+10
  • lukas.k
  • Veeam Vanguard
  • 205 comments
  • January 9, 2025

Hi ​@krischeu,

Easy fix: You have to modify a registry value to allow other users (other than the local built-in admin) to access the admin share (C$) which is required for AAP backup. Here you find the article and registry value:

LocalAccountTokenFilterPolicy accessing the C$ with a local account

 

Best regards

Lukas

LK | Veeam Vanguard | VUG Leader - Cyber Security Space | Security Specialist
Dynamic
C
2 people like this
  • Dynamic
    Dynamic
  • C
    Chrissawi
regnor
Forum|alt.badge.img+14
  • regnor
  • Veeam MVP
  • 1354 comments
  • January 9, 2025

Hello Heinz, this could be caused by the User Account Control on the Windows 2019 server. In detail it’s described in the following KB article: https://www.veeam.com/kb4185

Max M. | Systems Engineer @Veeam | VMCE/VMCA | VeeaMVP 2023 | former Legend & Vanguard
Dynamic
1 person likes this
  • Dynamic
    Dynamic
J
  • jotge
  • New Here
  • 2 comments
  • January 9, 2025

Hello Heinz,

based on your description - if the server is not a domain member - this is expected behavior. The cause is here: https://docs.microsoft.com/de-de/troubleshoot/windows-server/windows-security/user-account-control-and-remote-restriction

 

You can work around the problem by setting the following ReKey:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Entry: LocalAccountTokenFilterPolicy DWORD32 
Value: 1

...can also be found in the Microsoft article.

 

Regards 

 

Jan

Comment


Terms & Conditions