5 Replies Latest reply on Oct 24, 2014 8:58 AM by sinjen

    Pre and Post Tasks?




      New to Solar Winds Patch Management and have a question about pre and post installation tasks. I have a typical scenario where before I reboot a server I need to shutdown a particular service before a reboot can occur. This is necessary because the app in question is poorly written (and yes, we are stuck with it) and if not shutdown prior to a reboot, can at times corrupt its database. So, is it possible to perform pre patch installation tasks before patches are applied?



      Edit: Solar Windows Patch Manager 2.0.2207.2 running on Server 2012 R2.






        • Re: Pre and Post Tasks?
          Lawrence Garvin

          So, is it possible to perform pre patch installation tasks before patches are applied?


          It depends. The pre- and post-installation tasks declared via PackageBoot are per-UPDATE tasks. If you have a task that needs to be performed for a specific update, this is the tool for that job. However, the order of updates installed in a batch is indeterminate, therefore you cannot be guaranteed that the pre-installation task will run before ANY updates are installed, unless that update is the FIRST update installed. The only way it can be guaranteed to be the FIRST update is if its the ONLY update.


          However, the way I read your scenario is that you need to shutdown a particular service EVERYTIME you're going to do a reboot, so a patch package is not the place to do this anyway.


          One way you can address this issue with Patch Manager is this:

          1. Explicitly suppress the reboot when you do the patch deployment.
          2. After the patch deployment is completed, then STOP the service that needs to be stopped.
          3. Reboot the server using the Shutdown/Reboot task.


          The downside of this process is that it requires three different tasks to be initiated, in sequence, after confirming the previous task has completed.

          However, the tasks can be pre-defined and stored in the "Scheduled Tasks" collection (as DISABLED tasks), and then simply executed on-demand as needed.