According to the security best practice the VBR Server must not be domain joined: https://bp.veeam.com/security
How can I perform the PowerShell script against multiple VBR servers that are not AD domain joined?
-
- Enthusiast
- Posts: 95
- Liked: 5 times
- Joined: Oct 31, 2022 11:39 pm
- Full Name: Backup Administrator
- Contact:
-
- Veeam Software
- Posts: 2744
- Liked: 630 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Conencting and Executing Veeam PowerShell against non AD-Domain Joined VBR ?
Hi Backup.Operator,
Connect-VBRServer would be the way here, and as long as the server you're connecting from can reach these servers, you'll be able to connect to each VBR server and execute cmdlets against them.
Be sure to use Disconnect-VBRServer at the end of your script to terminate the connection.
Connect-VBRServer would be the way here, and as long as the server you're connecting from can reach these servers, you'll be able to connect to each VBR server and execute cmdlets against them.
Be sure to use Disconnect-VBRServer at the end of your script to terminate the connection.
David Domask | Product Management: Principal Analyst
-
- Enthusiast
- Posts: 95
- Liked: 5 times
- Joined: Oct 31, 2022 11:39 pm
- Full Name: Backup Administrator
- Contact:
Re: Conencting and Executing Veeam PowerShell against non AD-Domain Joined VBR ?
Thank you, @David.
What about the service account best practice?
I only know that the service account must not set with MFA
What about the service account best practice?
I only know that the service account must not set with MFA


-
- Veeam Software
- Posts: 2744
- Liked: 630 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Conencting and Executing Veeam PowerShell against non AD-Domain Joined VBR ?
You're very welcome.
No specific best practices from the Veeam side -- in current version the Veeam user used for Powershell must have Backup Administrator role. Audit the account activity and who has access to the account.
There are existing requests for more granular permissions, but nothing specific to share at this moment.
No specific best practices from the Veeam side -- in current version the Veeam user used for Powershell must have Backup Administrator role. Audit the account activity and who has access to the account.
There are existing requests for more granular permissions, but nothing specific to share at this moment.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: Bing [Bot] and 3 guests