My current monthly security patch setup contains a combination of MS and Adobe updates. 100% of the time, I get about 30% of my clients with a 413* return errors while deploying security patches to my client machines. It's typically due to the Adobe Flash updates failing because the clients browsers are open while LANDesk is attempting the install. This is very troublesome as you can imagine. Especially when we turn on Autofix > LANDesk finally finds the opportunity to install the flash update, and prompts the user to reboot after the flash update is installed. This annoys the end-users because instead of one reboot, they now have to reboot twice. (Once from the original security patch, and once for the flash update).
That leads me to my next question. Why does LANDesk need to reboot the client machine if all it's updating is Adobe Flash? I realize that my reboot options in the task is set to "Reboot - Prompt User", but that's because of the other MS patches actually require a reboot, etc. As I'm writing this, I realize that I can easily simplify this by separating the Adobe updates from the MS updates, but let's face it - that would be too easy and not enough fun. I'm hoping for some help with this issue.
Is there a way for my task to detect if the incremental update that's installed needs a reboot or not, and if so - it'll determine so when it's completed. Or there might be a way for LANDesk to detect if there are browsers open while the updates are trying to download, and then prompt the user to close their browsers so Flash can update? I'm looking for any solution, really. Fancy, simple, exciting, boring. Whatever works. We could make some fun of this and see how many feasible solutions the LANDesk community can whip up. Come on guys!
*413 = One or more patches failed to install