Hello there!
I've come up with an interesting problem which currently couldn't be solved by the Veeam Support Team so I thought I'll post this here and maybe I'm not the only one faceing this kind of obsticle.
Due FW restrictions and IP segementation my production B&R where the VirtualLabs for my VRO are running are not able to execute any verification steps/scripts.
F.e. the Verify Domain Contoller Port Step (https://helpcenter.veeam.com/docs/vro/u ... ml?ver=7.2) has the option to change the Execute Location but it's grayed out and according to the User Guide this option is not editable.
![Image]()
Why is that?
I mean why implementing this option when I'm not allowed to use it?
In our case we could simply change the Default Value to the Orchestator Server and are good to go.
But it's not just the DC Port Step - DNS, SQL, etc have the same option but still grayed out.
Can anyone shed a light on that matter for me?
Anyone else has this kind of "problem?
I've come up with an interesting problem which currently couldn't be solved by the Veeam Support Team so I thought I'll post this here and maybe I'm not the only one faceing this kind of obsticle.
Due FW restrictions and IP segementation my production B&R where the VirtualLabs for my VRO are running are not able to execute any verification steps/scripts.
F.e. the Verify Domain Contoller Port Step (https://helpcenter.veeam.com/docs/vro/u ... ml?ver=7.2) has the option to change the Execute Location but it's grayed out and according to the User Guide this option is not editable.

Why is that?
I mean why implementing this option when I'm not allowed to use it?
In our case we could simply change the Default Value to the Orchestator Server and are good to go.
But it's not just the DC Port Step - DNS, SQL, etc have the same option but still grayed out.
Can anyone shed a light on that matter for me?
Anyone else has this kind of "problem?
Statistics: Posted by Eric_Cartman — Mar 13, 2025 1:48 pm





