We have custom recovery step, which includes Powershell script to do DR for our database servers. Since this script has to be executed under specific account I've followed these commendations:
I am facing a problem where SRM executes this step and moves to a next step, thus not waiting for a script (i.e running task) to finish executing. How do I specify "delay" before moving onto the next step.
The scheduled task is probably backgrounded. You would probably need to either put a prompt so that you can manually validate the script is done or do another call out step that checks that the previous scheduled task finished before exiting.
The scheduled task is probably backgrounded. You would probably need to either put a prompt so that you can manually validate the script is done or do another call out step that checks that the previous scheduled task finished before exiting.
Very good solution but it seems better option would be to change SRM service account. Does anyone run SRM as a dedicated account (other than default Local System)?
I do run it as a Windows Service Account for this reason (though I haven't done a call out yet), modify the service directly, don't go through the modify/change installer.
Chris is right that you can change the account via the services console directly.
If you are using SQL server with integrated authentication you do need to ensure that the account you are running under has appropriate access to the database, see the installation guide for a detailed list of pre-requisites -> Requirements when Using Microsoft SQL Server with Site Recovery Manager
In the just release SRM 5.8 we enable you to set the service account as part of the installer itself.
