This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Pre and Post Tasks?

Hi,

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.

Thanks,

-Bo

  • 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.

  • Lawrence,

    Thanks for your reply. It's unfortunate that there's no simple way to do pre/post tasks prior to a batch of patches going out, it would be a helpful feature IMHO. As to your advise, they way I read this is that the running of the tasks you mentioned are a manual process? That's certainly something I have to avoid with about 1000 machines to manage. No, not all of them need this type of process, but I still need to keep it all automated as much as possible. We may try and get creative with the windows task scheduler and start stop services based on some event. Perhaps we'll just block out some time for that service to be down since it's not a 24/7 process.

    -Bo

  • I'd recommend taking a moment to create an idea for Patch Manager.  That way other community members vote on the feature. As Product Managers and avid thwack users, we all look at these when reviewing new features going forward.

    If you haven't taken the time already, go ahead and review the current ideas that are open for voting.  Let your voice be heard!

  • There is already an idea in the list that can be voted on.

    https://thwack.solarwinds.com/ideas/1840

  • Thanks Lawrence, upvoted.

    -Bo