Coming Soon: Reboot Deferrals and Custom Notifications

We’re happy to share that we’ll be releasing a new option that allows you to configure and have more control over system reboots after a patch update. The ability to defer system reboots has been a long-standing request from our existing customers, so we’re excited to be delivering this capability next week.

The new reboot deferral options will be available when you create or edit a policy. This new feature allows system administrators to configure a maximum number of reboot deferrals and the delay intervals for those deferrals. If an update to a current device requires a reboot, the device owner receives a notification that a reboot is required. If reboot deferrals are configured, they have the option to reboot now or defer the reboot for a set amount of time, a set number of times.

You do not need to do anything to prepare for this feature being released. All policies will maintain their current settings. Once the console is updated, you can create new policies or edit existing policies to take advantage of this new reboot deferral capability.

The image below highlights the changes you will see on the Create Policy page, showing reboot notifications and deferral settings both enabled.

7 Likes

Any way to display a notification on Linux (Ubuntu)?

Is there still a 15 minute timeout where it will force an action if the user doesn’t respond?

It will behave like the patch notifications do now, where you can give them options to defer for 3 different time options, and you can specify the number of deferrals. Only when they use up all their deferrals will they be forced to reboot.

Edit: As @bryanhackett mentioned below, if the user ignores any of the notifications then after 15 minutes it will indeed assume that it can proceed with patches/reboots.

Unfortunately not - we don’t have parity on the Linux side for this feature yet.

Yes, if enabled - The user has ~ 15 minutes from receiving the notification to differ the reboot. The machine will automatically reboot if the user takes no action.

2 Likes

Also, is this behavior what you would want to happen, or would you prefer that missing the 15 min window defaults to a deferral instead of a reboot? Or would you want the option to configure that differently depending on your needs?

1 Like

Thank you for confirming!

1 Like

Would be nice to have some control over that. Users get pissed when they use the washroom and get a reboot.

Yeah I can see that happening, and we’ll add that concept to the list of future improvements for reboot notifications, for the next version of improvements.

1 Like

yet.

Does that mean this is planned?

Nothing definitive on the near term roadmaps yet, so I can’t hazard a guess as to when we’ll get to that one. What’s the use case for Linux for your setup? Do you have end users running Linux on the desktop that you need to send notifications for?

Yes. The majority of our end users are running Ubuntu Desktop as their daily driver.

Good to know. I’ll send that feedback over to the product team to incorporate into their prioritization and triage process.

You can find our documentation that will help you understand Reboot deferral and custom notifications here:

https://docs.automox.com/home/system-management/managing-policies#managing-end-user-notifications

2 Likes

Glad to see this new feature! But I agree that forcing the reboot if no response in 15 minutes is still an issue. Defaulting to the configured deferral settings would be better than forcing a reboot in 15 minutes (when they may have stepped away). Having the ability to customize/configure that setting would be even better.

1 Like

Thanks for adding your vote to that option - I’ve passed that long to the product team for future improvements to the reboot notifications.

Ok the product folks have made a ticket in Productboard that you can both vote for, as well as enter your email to be notified if/when it gets done:

Feel free to add your votes to that and any feedback you have on how you’d like it to function.

2 Likes