Feature Request: Customize timeout used on post deadline prompts to a value other then 2 minutes

[quinningtime]

I would love to see the ability to customize the dialog timeout value used after a deadline has passed to be a value other then 2 minutes or 120 seconds. For various reasons from softwareupdate binary failures to vacations users will find themselves past the zero date deadline set in superman and will get a prompt saying Update X needs to install and the deadline is past. They only have 2 minutes to respond to this dialog before their computer is restarted. I would like to be able customize this dialog timeout to a larger value to give them more time to prepare for the restart while still not allowing them to defer any longer or dismiss the dialog without restarting.

Thanks
Quinn

[Macjutsu]

Are you using a soft deadline or a hard deadline?

[quinningtime]

I am using a Soft Days Deadline with a Soft Deadline Dialog Timeout set which causes it function like a hard deadline after the 2 minutes.

Which I like because there are those folks who are somehow willing to leave a dialog open on their screens on the side for incredible amounts of time to avoid a restart but I would like to say set it so if they are past the deadline a restart is happening no matter what but they get for example 30 minutes rather then 2 minutes before the forced restart.

[Macjutsu]

Then just set the Soft Deadline Timeout to 30 minutes. I don't see what needs to be changed here except your settings?

[quinningtime]

I do have the Soft Deadline Timeout configured to a longer time. But if the the soft days or date deadline has passed any soft deadline timeout setting above 120 seconds is reduced to 120 seconds and for various reasons some percentage of my users get past the set deadline without installing the required update and then have only 2 minutes from notification to forced restart.

[Macjutsu]

Ah ok... now we're getting somewhere. I wrote that code so long ago I forgot it did that automatic cut over to 120 seconds.

Ok... I'll reevaluate this logic. Seems like a more logical behavior would be to only do that cut to 120 seconds if you don't have a specific timeout option specified.

In other words, if you specify a 30 minute soft deadline timeout... then it should do that every time.