2 of 2 people found this helpful
Calling remote locations during a Customer Action tend to fail due to permissions issues. I would suggest that you setup a Custom Action Push File task to copy the batch file to the target machine. The batch file will be placed in the correct folder location on the target machine in C:\Windows\ProPatches\* The command would be: (%pathtofixes% is automatically set during the deployment)
You should also setup a Push File task to for the PS1 file so it can run locally on the target too. The file will also be copied to in the %pathtofixes% location.
It would look like:
- File Push for service_stop.bat
- File Push for the .PS1
- Before any patches task for: call %PATHTOFIXES%service_stop.bat
Let me know if you have any issues.
Thanks Charles, that was just the type of answers I was looking for. Awesome stuff, great detail. All of the information I need to make it happen, I really answers in a forum which do not assume I know something!
Any time, let us know if you need anything else or run into issues implementing this.