Objective
To explain how Automatic Restarts behave on Linux endpoints managed by Automox patch policies and outline key feature differences compared to Windows and macOS.
Overview
When an Automox patch policy with Automatic Restarts enabled executes on a Linux device, reboot triggers are evaluated based on system package update flags upon policy completion.
Key Operational Behaviors & Limitations
Post-Policy Reboot Evaluation: A reboot is triggered automatically at the end of a policy execution cycle if any package or kernel update applied during that run flags the device as requiring a restart.
No End-User Notifications: End-user reboot notifications are not supported on Linux OS endpoints.
No End-User Deferrals: End-user reboot deferrals are not supported on Linux OS endpoints.
ℹ️ Note: End-user restart notifications and deferral prompts are available exclusively for Windows and macOS endpoints.
Best Practices for Linux Reboots
Because Linux policies restart devices immediately following a required patch without end-user warnings or deferral options:
Schedule Maintenance Windows: Schedule Linux patch policies during designated off-peak maintenance windows (e.g., overnight or weekends) to minimize workflow disruption.
Use Pre-Reboot Worklets for GUI Desktop Users: If deploying to interactive Linux desktop environments where user warnings are required prior to a reboot, utilize a custom Worklet to display desktop alerts before triggering restarts.
Related Articles