how-to · machine Open this in the console

Set a time when a machine reboots.

Work › actions › alerts › scheduled reboots. Pick the day, the start time and how long. Times are the company's time zone.

Inside the window the hub waits instead of raising a critical downtime alert. If the machine is back before the window ends, it records a scheduled reboot in the history and BE AI checks the machine came back healthy. If it is still offline when the window ends, the critical alert opens as usual, titled did not come back from its scheduled reboot.

Find scheduled reboots

Open the machine, then work › actions, and open alerts. Scheduled reboots lists the windows this machine has. Accounts server already has one: Sundays 03:00–04:00, marked learned because the hub switched it on from the machine's own reboots. The time zone is shown in the heading.

Scheduled reboots on Accounts server with a learned Sunday window and the add form — Accounts server with one learned window on Sundays.

Add the window

Choose the day (or every day), the start time and how long the reboot can take, then press add window. It saves at once. Leave enough time for updates to install and the machine to start again. Remove takes a window off.

Scheduled reboots with a new every-day 02:00–02:30 window — Every day 02:00–02:30 is added under the learned Sunday window.

The hub can also find the window by itself: Let the hub learn when a machine reboots. A desktop that is simply off at night is Leave a desktop out of offline alerts.