May have found a bug - Windows Workgroup Machines

[pmichelli]

I am not sure if this is a support issue or not. I can certainly open a SR if you deem necessary and have it routed to engineering. I have stumbled upon what I think is a bug.

EDIT : Case opened 07597253

My Veeam server and proxies are not domain joined. We keep them in a workgroup on the same vLAN. When I try and add a Windows 11 machine to act as a backup proxy, I am unable to use any account other than local administrator.

I created a service account on each of the Windows 11 machines locally and added it to the administrator group. I have verified that I can RDP to these machines from the VBR server.
No matter what I do, it will never add the machine, it keeps saying failed to connect to \\IPofWindows11\ADMIN$ from the VBR server.

If I open a file explorer and \\ipofwindows11\ADMIN$ from the VBR server and enter the service account credentials windows11host\serviceaccount and the password, it maps the ADMIN$ share. So there is no issue with the Windows 2022 VBR server trying to map ADMIN$ on the Windows 11 machines.

This caused us some issues as we upgraded from 23H2 to 24H2 on the Windows 11 proxies and it disabled the local admin account and broke the backups until I was able to figure it out and re-enable the local admin account.

Best practice (administrator is disabled by default in Windows 11) is to use a service account, but I can't get it to work at all. It won't even scan the ports when I try and add the Windows 11 server. Tried with firewall off as well and still same issue cannot connect to ADMIN$

I can easily reproduce this on a call with someone .. I even went as far as spinning up a brand new Windows 11 machine, created the service account, added to local admin group and no luck.

How should I proceed to get this looked into?

Thank You

[Mildur]

Hello pmichelli

That sounds familiar.
It’s a known situation where you have to disable remote UAC restrictions on the remote machine to make it work under a different account than the „default administrator“: https://www.veeam.com/kb4185

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

Best;
Fabian

[pmichelli]

@Mildur

You are the best !! I have been banging my head on this off and on for days now. This worked. Thank you so much for replying !!

[Mildur]

You‘re welcome

Have a nice weekend,
Fabian