(imported topic written by andyt001)
Hello all. I have a question regarding baselines and post-actions.
Per the recommendations for baselines (click the link below), the post-action should be set to do nothing after the baseline completes. Does anyone know the reason for this and what should be done instead so that the user eventually reboots?
(imported comment written by DanPaquette)
Hi Andy,
Others may chime in, but here is my take.
You can set the baseline to reboot via the post action tab and specify the deadline for a user to reboot. Keep in mine that depending on how you set up your baseline action, the system could reboot and start delivering additional patches from that baseline that were not relevant before due to a pending restart flag or dependencies on other content in the baseline - and then the user would be requested to reboot again with the same deadline options. This has potential to be highly interrupting to the end users whose endpoints are significantly behind on patch content. Imagine suffering through two or more reboot requests when you return from a two week vacation.
I had one customer who simply executed the “restart computers” fixlet once a week with a two day deadline. This would ready the endpoints for the next patch action so that systems in pending restart status could report prior/final results and show relevant for new or existing baseline content.
For servers, this is less of an issue… shouldn’t be end users logged into a server and security requirements would mandate a reboot to facilitate the proper patching and configuration during the shutdown and start up process.
(imported comment written by andyt001)
Thank you Dan. That answers my questions. Good information.