Pre and Post actions during patching
We have a need to run a scripted action [i.e. Ability to run one or more .ps1 Powershell scripts/vbscripts/batch files/cmd files] both before patching and after patching on specific machines that receive a SUG deployment.
These actions can be for a variety of reasons:
• Reboots before patching
• Stopping services or other applications processes
• Read server state and making sure it is set correctly after patching is finished
Currently we reboot 90% of our fleet before running patching to make sure system memory (we check memory?) etc. are clean, to allow the best possible patching result.
We have some systems that need a service shut down via a script as the stop action of the service requires a password. Or we have an application that needs to be stopped cleanly before patching can proceed successfully.
Also, with SQL clusters (and some other systems), we want to record the current state of the environment, patch, reboot and then make sure the server is set back to the recorded state or services and system are returned to a working state.