Systems Management Question

Patch Schedule - Reboot set to prompt. What's the expected behavior after all reprompts?

01/28/2015 1523 views
What is the expected behavior after all reprompts have gone through for a schedule set to Prompt?
Is there a way to set it to prompt X times and not reboot if someone has clicked No at every prompt?

I always thought it would stop prompting and not reboot. But what I'm seeing is that it reboots at end of all the reprompt interals. 

I had our reboots set to Prompt with a Timeout at 5 mins, Number of reprompts at 5 and reprompt interval set to 5 mins for a group that we wanted to be sure to see the notices but also be able to continue working without them if they needed to, hence the low numbers.  But after clicking 'No' 5 times, a machine was rebooting by the AmpAgent (so say the local even logs).

I changed the settings to what is shown below for now.


0 Comments   [ + ] Show comments


All Answers

So I think your question is about "Number of prompts"

The answer to that is when it reaches that number  a reboot is forced. Think N-1. N= the number of prompts. They have that many chances to hit No and based on your image, they have 7 changes to hit No on the 8th prompt the reboot is forced. 

Typically in other areas of the KBOX you can set it to zero which tells the system to keep trying but I don't know if that would work here as there is nothing in the documentation listed for that. A quick email to support might provide the answer. 
Answered 01/28/2015 by: nshah
Red Belt

  • Thank you much for the clarification. I'll check in with support on the zeroing option. I thought it was an option when we first stood these servers up, but who knows now. That would be preferable. I'll report my findings here.
I've checked with support on this in the past. At one point there was an update where this changed...there used to be an unlimited option but now after the number of prompts is hit a reboot is forced. I didn't like it at first but we just had to adjust to it. I changed our message to let users know the reboot is inevitable. You can just set your prompts really high. In our case we alert them of a reboot after 1 week of hourly prompts but actually set it to 10 days for some leeway and weekend wiggle room. Turns out for the good though as you do need a reboot for patches to finish and a system could be unstable in that state.
Answered 01/28/2015 by: jegolf
Red Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ