Reboot System

What the Linux Reboot Worklet does

This Automox Worklet™ executes a scheduled system reboot on Linux endpoints using the shutdown command with a configurable delay. The Worklet supports a default two-minute delay before initiation, giving running processes time to gracefully terminate.

The remediation script uses the Linux shutdown utility to trigger the reboot. You can customize the delay parameter to match your maintenance window requirements, ranging from immediate (zero-minute) to longer delays for complex shutdown sequences.

The Worklet works across all major Linux distributions supported by Automox, including RHEL, CentOS, Ubuntu, Debian, SLES, Fedora, Amazon Linux, AlmaLinux, and Oracle Linux.

Why schedule reboots for Linux maintenance

Linux systems require reboots to complete kernel updates, apply security patches, activate configuration changes, and resolve system-level issues. Automating reboot scheduling through the Worklet reduces manual intervention and maintains consistent timing across your endpoint fleet.

Scheduled reboots allow your IT operations team to coordinate system downtime during low-usage periods, protecting against operational disruption. This approach is particularly valuable for managing distributed endpoints where coordinating individual reboots would be time-consuming.

The configurable delay parameter gives your endpoints time to gracefully shut down running services and save application state before the system restarts, reducing data loss risk.

How Linux reboot scheduling works

1. Evaluation phase: The Worklet checks system availability by exiting with a status that indicates reboot is required. This signals Automox to proceed with remediation on compliant endpoints.

2. Remediation phase: The Worklet executes shutdown -r [minutes], initiating a scheduled reboot with your specified delay. The system broadcasts a warning message to all logged-in users before proceeding.

Linux reboot requirements

• Root or sudo access on target endpoints

• Supported Linux distributions: RHEL, CentOS, Debian, Ubuntu, SLES, Fedora, Amazon Linux, AlmaLinux, Oracle Linux

• shutdown command must be available in system PATH (standard on all Linux distributions)

• Optional: Customize the delay parameter by editing the shutdown command (default is 2 minutes)

Expected system state after reboot

After the Worklet executes, your endpoint will initiate a scheduled shutdown sequence. All logged-in users will receive a broadcast warning message displaying the reboot countdown. The system will gracefully terminate running processes and services during the delay period.

Once the delay period expires, the endpoint restarts and boots into a clean state. All pending kernel updates, configuration changes, and patches take effect during this restart. The endpoint rejoins the network and resumes normal operations once fully booted.

How to validate reboot system changes

1. Run this Worklet on a pilot Linux endpoint and review evaluation output for reboot system.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as exit.

4. Validate remediation effects from script operations such as shutdown, then rerun evaluation for compliance.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for reboot system. This supports repeatable maintenance tasks workflows, faster change control review, and auditable compliance evidence.

Useful script references for this Worklet include evaluation operations such as exit and remediation operations such as shutdown. Use these indicators to verify that endpoint changes match intended policy outcomes.