rpc error agent domain controller

[matteu]

Hello,

I migrate my customer from veeam in domain to veeam in workgroup and replace all account with full admin right with only what they require.
Veeam is in V11.

Since the swap, only 2 of his physical DCs are backup OK with veeam agent.
All 10 other physical doesn't work.

All the DCs use the same account (builtin\administrator member). I try with domain admin account but same issue.
When I launch job, it fails after 2/3 sec only because he say he can't connect to the remote computer.

On the log I can see :
ERR |Access denied
[09.09.2021 19:31:50] < 3496> dpl| >> |RPC client is not a member of built-in Administrators group.
[09.09.2021 19:31:50] < 3496> dpl| >> |--tr:Error code: 0x80070005
[09.09.2021 19:31:50] < 3496> dpl| >> |An exception was thrown from thread [3496].

It's like veeam doesn't use the good account...
I repeat, the same account is used for ALL my DCs...

I tried to uninstall veeam agent and install it again but same issue happen.
I don't know what is different between these 2 DCs and all the others.

When I try to test connection on the protection group, it's OK for all the 12 DCs
When I rescan the protection group it's OK for the 12 DCs.

My client opened support case wednesday, I will write here the number on monday but maybe you have some idea ?

[Mildur]

Have you tried the solutions from that topic?

vmware-vsphere-f24/rpc-client-is-not-me ... 20775.html

[matteu]

Hello,

I found this post.
There are lot of solutions on it.

net localgroup Administrators /add domain\username -> This can't be different between DC because I use GPO on domain controllers OU to put my service account on "builtin\administrators" group.
and the account is member of my builtin\administrators group.

check if the account that Veeam Backup and Replication is running under is in Administrators role on host machine and backup repository machine -> I don't know what it is talking about. VBR is on workgroup and is running on local system. Then, it's working on 2 DC and not on the other... DC replicate group membership, it can't be the reason. Same explanation for repository (dxi in my case)

backup user not having admin rights on the Veeam proxy server -> When proxy are on workgroup and you want to backup DC, it's impossible the service account to backup the DC to be proxy server local admin. Then, it's working on 2 DC why not all the others...

The only logical possiblility I found is this one : veeam-agent-for-windows-f33/veeam-agent ... 69693.html
My both working DC have registry key to 0 and all other have nothing.
I launched windows update on 1 not working backup DC and I will try with registry key value to 0 and see if this change something or not.

I will try to test it on a lab too and see if I can reproduce the issue.

[matteu]

Case number : 05014996

[Dima P.]

Hello matteu,

Based on the case details I see that the issue was resolved by updating the accounts for machines in the protection groups. Please let us know if everything works correction now or you need any further assistance. Thanks!

[matteu]

Hello,

Yes, I finally find the answer.
Customer had custom protection group + Manually added protection group.
Domain controllers were on both protection group and job uses account from manually added protection group.

I update job with "test computer" remove computer from manually added protection group and then from custom protection group add computer to the job and finally delete "test computer" from the job.

[Mildur]

Thanks for the update