Custom Step not performing required actions

[danielmx1]

Hello guys.

I have a custom script that's supposed to replace some string from a config file inside a VM but behaves differently when executed from either Powershell ISE vs Orchestrator Recovery Plan.

- When executed from Powershell ISE, script runs successfully AND replaces string and overwrites changes to file (as expected)

- When executed from VRO Recovery Plan, script runs successfully (that's what the Recovery Plan execution report says) but does not replaces string nor writes any changes to file, it stays

Both script tests are executed from Orchestrator server with same user and I'm using the same credentials to connect to vCenter and VM as well.

Is there something that Orchestrator does differently than Powershell ISE when running a powershell script? Maybe loading different modules?

Thanks

[Alec King]

Hi Daniel,

Can you confirm some things about your script?

- Does it execute on VRO server? Or in-guest?
- Does it use passed-in or hard-coded credentials? Or default (which would be VBR service account)?.
The credentials could be one difference between execution in VRO and execution in PS ISE in your user session.

- Have you added logging to your script? You can use commands Write-host, Write-error, and Write-warning to capture more details which will be shown in VRO UI and reports.

If you could share an (anonymized) version of your script that would also help us analyse this.

Thanks!