I can imagine perhaps what's happening in the background, but typically such intentional limitations are handled with proper error messages instead of what looks like a Windows error bubbling up into the console.
Please share your case number once created. Thanks!
David Domask | Product Management: Principal Analyst
I suspect the problem is because accounts that end in $ are typically machine account's so they added filtering to reduce the listing to just users.
User accounts ending with a dollar sign ($), also known as “hidden accounts,” are designed to imitate machine accounts typically found in AD environments.
I've personally only found malicious actors using $ at end of name to try and bypass monitoring and security solutions and I believe that was one of the big Active Directory patches in last few years because it was causing AD to treat users with a $ as a machine account and giving that account elevated permissions. I just can't remember the details.
I would never recommend admin accounts have a $ at the end personally.
Thanks Rumple, I understand where you are coming from.
For clarification, the accounts are prefixed with "adm$", so their account names are like "adm$john.smith".
It isn't a big deal, we keep Veeam separated so its not on the domain, therefore we can rename the accounts or create new ones on the Veeam B&R server.
hps_stevea wrote: ↑Jan 12, 2026 10:38 am
I have reverted my admin account name back to adm$, recreated the issue and raised a support request. Case #07946559
[Moderator: Replaced Support ID with Case Number]
Support confirmed this is a known issue that has been reported to our RND team, planned to be fixed in a future release. Thanks for reporting the issue hps_stevea.
David Domask | Product Management: Principal Analyst
