VBR v13.0.1 still expect a standard account for listing and handling Windows cluster.
Two places to set the account both require a account for managing such backup
* Master account, used for listing AD-object for backup (?)
* Custom Credentials for managing object, if not set it uses Master Account
There is no selection to use Veeam certificate based login (Deployment Kit), which can be selected for Windows Agent.
The closest workaround would be to use GMSA accounts, but these does not work as expected in our environment where the VBR server is not AD-connected as per best practise.
I would like to be able to use Veeam certificate based login on all our servers. AD listing of cluster objects could be an account with lesser priviledges.
As a side bonus that makes it easier to work across several AD forests.
-
dejan.ilic
- Enthusiast
- Posts: 52
- Liked: 5 times
- Joined: Apr 11, 2019 11:37 am
- Full Name: Dejan Ilic
- Contact:
Who is online
Users browsing this forum: No registered users and 4 guests