VeeamOne: no connection to Backup&Replication

[dspringer]

VeeamOne bullies me.... I have a VeeamOne server that is part of the domain. I also have a VBR server that is not part of the domain. So far, so good.
If I use the local Windows administrator account, I can connect to the backup server without any problems. But now I want to harden the system a little and use a separate user.

I have already worked my way through the Veeam-One Guide :
https://helpcenter.veeam.com/docs/one/d ... rvers.html and also https://helpcenter.veeam.com/docs/one/d ... otely.html

So I have a new user on the backup server who now has the following rights:
- Groups: Administrators, Distributed COM Users, Event Log Readers and Performance Monitor Users.
- Within VBR, the user is assigned as a service account with administrator rights.
- WMI namespace and sub-namespacing is set with the rights ‘Enable Account / Remote Enable’.
- The authorisations for ‘Access Permission’ and ‘Launch and Activation Permission’ are also set in ‘dcomcnfg’. Likewise the settings in ‘Windows Management and Instrumentation’

I have also logged on locally to the backup server with the new user to test the login data correctly.

But when I enter this data in VeeamOne, I immediately get ‘Access denied. Please verify credentials and try again’. It doesn't matter whether I use ‘Server name/Username’ or ‘Username@Servername’.
The normal local administrator is also formatted in version 1 and works without any problems.

Could there be a problem because of the normal hardening of VBR since the new version? I have completed nearly all points of it.
Although I have to admit that I still have the firewall off - so this shouldn't be a problem because of blocked ports.

[RomanK]

Hello David,

Both links are correct, and following these steps should work. I implemented them in my lab about two weeks ago, and everything worked well.

From your description, everything looks correct.

Within VBR, the user is assigned as a service account with administrator rights.

Try to explicitly set the role in the VBR console menu > User & Roles for that user. Also, try to reboot the machine just in case.

If still nothing, you may open a support case and check with our engineers all steps to ensure there is no bug or something unpredicted or undocumented.

Thanks