Hello community,
After upgrading a Veeam Backup & Replication environment from version 12 to version 13, we started experiencing some unexpected behavior related to remote script execution, user permissions, and MFA. I’d like to check if anyone else has faced a similar situation.
Environment
- Veeam Backup & Replication recently upgraded from v12 to v13
- Monitoring solution relies on PowerShell scripts executed remotely
- Use of Operator role / custom non‑Administrator users
- Scripts used for status collection and integration with external monitoring tools
- Issue 1 – Remote Script Execution
After the upgrade to Veeam v13, scripts no longer work when executed remotely unless the user is a Veeam Backup Administrator.
- Before (v12):
✅ Scripts worked with Operator or custom roles - After (v13):
❌ Scripts only work when executed by a Backup Administrator
❌ Direct impact on monitoring (scripts no longer return data)
- Error Message
When attempting to run PowerShell commands using a non‑administrator account, we receive the following error:
This indicates that, starting with v13, the Veeam PowerShell Snap‑in now requires the Backup Administrator role exclusively, even for commands that previously worked with reduced permissions.
✅ How are we operating in this scenario?
Based on the scenario described above, we are creating a dedicated service account with the Veeam Backup Administrator role, with MFA disabled, to be used exclusively for PowerShell automation and monitoring scripts.
We are validating the monitoring via API. Currently, the entire environment is monitored via Zabbix.
Has anyone else experienced this? Did they take any different action?
