Pending reboot detection

Know what is really waiting.

Reboot IQ combines Automate’s native state with 14+ additional reboot indicators, so a single PendingReboot flag is not the whole picture.

The queue is the working list. Sort it, open a machine, and act without leaving Control Center.

Cause

Read why the restart is pending.

Each machine shows a plain-English reason and how long it has been waiting. Aging buckets put the oldest wait first.

The update is installed and still waiting on a restart.

A servicing stack change has not finished until the reboot.

Files are staged to replace on the next start.

The join completed in the directory and still needs a restart.

An installer left a reboot marker the native flag can miss.

Local time

A fleet set for 11 PM reboots each endpoint at its own local 11 PM. No shared UTC timestamp, and no timezone spreadsheet.

Client A11:00 PM local
Eastern endpoints restart on their own clock.
Client B11:00 PM local
Central endpoints do not inherit another office’s hour.
Client C11:00 PM local
The same policy travels across time zones.
WindowMaintenance hours
Servers stay inside the window already agreed with the client.
StaggerNot the same second
A large group does not reboot all at once.

Policy

Group machines the way the MSP already works, then apply one restart policy.

Keep server restarts inside the hours the client already approved.

Overdue machines can be scheduled automatically instead of sitting in the queue.

Daily, weekly, or monthly policies continue after the first restart.

Audit

Calendar, history, and the audit log record who scheduled, cancelled, or forced a reboot, and why. History includes CSV export for a client review.

Alerts — and optional tickets — can open past a threshold and close when the reboot completes.

Detect, explain, schedule, and verify without a second endpoint agent.

View pricing