Add the ability to associate a script to a Patch Schedule
I would love to have the ability to run a script as part of a patch schedule and have it run before the patching begins.
The example I have in mind would be for patching BIOS on computers using Bitlocker. I could have a separate patch schedule for BIOS patching only and have a script set to run prior to patching that would suspend bitlocker and enable it after the next reboot. With it being integrated with the patch schedule, I would not have to worry about the bitlocker disable script running needlessly.
I am doing something similar with scripts, but it is a pain to manage because I have to tweak for different computer and versions of bios.
This would solve a number of issues having pre and post options for running a script. It would also provide a solution to this feature request https://kace.uservoice.com/forums/82699-sma-k1000/suggestions/17526076-suspend-bitlocker-as-part-of-the-patch-detect-de
Phil Brandvold commented
This would be a very helpful tool. We have users ending up with Bitlocker problems because we can't suspend bitlocker before patches in a dynamic or flexible way.
Using PowerCLI scripts to snapshot a VM before patching would be useful. If you could call the Patch Schedule with the script as a task that only continues if the snapshot task completes successfully.
Tim Lawhead commented
The ability to have a workflow for patching allowing Scripts before or after the Detect/Deploy or Deploy schedules would be very useful for my site, both before and after patching. We run scripts for some systems before patching to manage services and applications that need to be turned from automatic to manual start during reboot cycles and then after patching to turn those services back on and/or reboot applications/database servers in a set order to restore application functionality and provide notification upon error/success.