Modify PowerShell command used to run scripts so that errors occurring outside the script itself can be caught

[anon38822071]

It’s something I mentioned in this thread:

Scripts showing as "Successful" even when they fail because script execution isn't allowed

@mgiordano RE: context - I run basically every script under system context. I do have one script I run under user context and it fails if no one is logged in, but I’m fine with it. Its only purpose is to display something to logged-in users, so if no one is logged in I don’t care. Also, execution policy can apply to the system account. There are separate policies for User and Machine. For example: get-executionpolicy -list Scope ExecutionPolicy ----- --------------- Machin…

I’ve personally had quite a few issues with scripts silently failing. There are a number of ways a script can fail and still be reported as a success, even if a script is written to handle errors.

1. Something prevents the script from running, such as execution policy.
2. A script runs into an unhandled exception/terminating error before it can pass an error code to the parent session.
3. The module.psm1 file is corrupted or removed by an over-zealous anti-virus solution.

These are all situations I’ve run into, and all situations where Syncro reports a success when the script run is actually failing. All my suggestion is doing is making use of additional information about errors that the system is already providing in the parent PS session, but that we as Syncro customers are not able to access because of how the system currently works.