Trying to move to gMSA - getting lots of errors

[mvalpreda]

Case 08085333

Environment:
2019 Hyper-V server for production
2019 Hyper-V server for replication
5x VMs - including 2x DCs (mix of 2016/2019/2025)
VBR 12.3.2.4165 VM
All are domain joined (including VBR server for now)

Looking to move to gMSA, went through the directions at
https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
and when I do a credentials test, I keep getting

5/6/2026 2:48:53 PM Failed Checking standard credentials 0:00:13
5/6/2026 2:48:53 PM Failed Connecting to guest OS via RPC 0:00:01
5/6/2026 2:48:53 PM Failed Testing admin$ share accessibility via RPC 0:00:01
5/6/2026 2:48:54 PM Failed Cannot connect to the admin share. Host: [MAIL02.domain.com]. Account: [domain\gmsa.veeam].;Failed to perform safe logon;Failed to create a process token for account domain//gmsa.veeam$;Win32 error:Access is denied.; Code: 5
5/6/2026 2:48:54 PM Failed Cannot connect to the admin share. Host: [192.168.0.16]. Account: [domain\gmsa.veeam].;Failed to perform safe logon;Failed to create a process token for account domain//gmsa.veeam$;Win32 error:Access is denied.; Code: 5
5/6/2026 2:48:54 PM Failed Connecting to guest OS via Guest agent 0:00:12
5/6/2026 2:48:54 PM Failed Testing host accessibility via Guest agent 0:00:12
5/6/2026 2:49:06 PM Failed Cannot connect to the guest agent service. Host: [MAIL02.domain.com]. Account: [domain\gmsa.veeam].;Failed to reach the Deployment service
5/6/2026 2:49:06 PM Failed Cannot connect to the guest agent service. Host: [192.168.0.16]. Account: [domain\gmsa.veeam].;Failed to reach the Deployment service
5/6/2026 2:49:06 PM Failed Failed to validate credentials and connectivity

All VMs, hosts, and the VBR server are in the gMSAComputers security group.
Test-ADServiceAccount gmsa.veeam shows TRUE on the VMs I am testing.

Not sure what might be going on, or if there are better directions on how to set this up.

[david.domask]

HI Mark,

Thanks for sharing the case number and details, and sorry to hear about the challenges.

Please continue with Veeam Support on the case, as we will likely not be able to meaningfully troubleshoot over the forums, and unclear from just the above why the Access Denied errors are returning currently. I see the case was only just opened, so please allow Veeam Support time to review the most recent update.