Deadline-Based Interface Updates

Hi Jnecco,

You’ll find a bit of insight in our KB article  here: https://docs.automox.com/product/Product_Documentation/Notifications___Restarts/End_User_Notifications.htm

The notifications are designed for compliance enforcement, if a device goes offline longer than the deadline, a reboot would occur the next time the device checks in. If there is a multi-day deferral (24+ hours), the end-user would repeatedly see pop-ups with a clear deadline highlighted.
You can make the deadline as long as you want, between 1 to 240 hours.
If you find people are seeing reboots upon logon, simply lengthen the reboot deferral from 9 as an example to 18 or so. The KB describes the notification frequency, which gets displayed more as the deadline gets closer.

Bottom line, no one should receive a surprise reboot, and the deadlines make it clear that if a reboot isn’t initiated by the end-user, a reboot will be enforced. 

This also doesn’t have to be the behavior though. Disable the patching reboots if you would like, in favor of a bi-weekly (or so) reboot at ‘X’ time on ‘X’ day, so it is even more predictable. We have templates in the Worklet Catalog for those.

We can help clarify any other questions you might have. Just reply here.

Regards,

Mark

Hi ​@Jnecco! 

Do you happen to know which University modules still referenced the old deferrals? I’d like to pass it along to the team if possible so we can get those updated.

 And like Mark said any other questions you have, let us know!

Best,

Jared

Sure, ​@AX-JaredHines. I’ve already submitted the information in the survey at the end of the module, but it is the “Best Practices: Scheduling and Notifications” module.

https://university.automox.com/best-practices-scheduling-and-notifications/2105351

I appreciate it! I’ll get this passed along!