Replies: 1 comment 2 replies
-
Hey Shane,
As for the storage medium for update successes, I would suggest something more resilient to overwriting. If we only focus on failed action (f.ex. to start thinking if we should retry or manual intervention will be required), the the best pace would be a HKLM registry Key with subkeys names after App.ID with reg value called "state" or something similar. Then you would only need to do is querying the registry key, doing the "foreach-object" check of reg values. Just thinking aloud.. |
Beta Was this translation helpful? Give feedback.
-
Thank you for creating the WAU! Has saved me a lot of time trying to create something myself.
I'm currently looking for a way to monitor for failed application updates with our RMM tool, ConnectWise Automate. My idea is to have the script write to the Windows Event Logs based on failures and successes.
After going through the scripts, I had an idea of adding some event log writing code to the Update-Apps.ps1 script.
Though you might want to integrate something like this in your release?
Here is my current versions of this that seems to be doing the trick:
Beta Was this translation helpful? Give feedback.
All reactions