Hello,
in my company, sometimes we use scripts (powershell) to achieve certain goals on target machines. Perfectly normal thing. But we would like to know when something goes wrong. Most scripts return success to sccm when finished, and monitoring such deployments give nice, green circles, and 100% compliance. That's because script deployed via package or application is always successful, unless something messes it up. We do have custom error handling, and logs for every script... but I would like to have a tool that allows me to see internal errors in the description of an event, returned in SCCM deployment monitoring pane.
The closest I managed to get with the issue, was using 'exit X' command in Powershell, when stumbling on an error. It does in fact show up as 'error' in SCCM monitoring pane, but I was not able to pass the description of the error in any way. SCCM simply uses exit code in the description column, and technician has to intepret it by self.
My question is - is there any known way, to pass application deployment errors to SCCM from inside of a script?
I really would like to pass exit code as a MessageID, and a string as a description.
