The option you can use to help with this is actually going to be within the patch deployment template that you use in your patch task within the agent policy.
In the deployment template that is used make sure to go into the "Post-deploy Reboot" tab and enable the check box for User may > Cancel action (patch installation will complete at next reboot). This allows the user logged onto the agent system to cancel the reboot for the time being.
I hope that helps.
1 of 1 people found this helpful
We deploy patches every night at 0100. This satisfies all of the various hospital departments, most importantly, labor and delivery.
Since you have developers running an all night rendering effort, I would capture these machine names and place them in a different machine group and patch on FRI-SAT-SUN night, as applicable.
Would these options require the user to be present when the patch process starts in order to cancel it?
I think I'm going to do a combination of the 2 suggestions
Under Post-Deployment Reboot I will set it to "Alert user, perform action when user logs off" and then make a separate agent policy with this deployment template for machines that need to be uninterupted. With this option if a reboot is required for patches they should just come in the next morning and see some screen on their computer telling them a reboot is needed to finish installation?
If the user won't be at their desk it would probably be better to use the option of "Alert user, perform action when user logs off".