This guide covers the behavior of manual policy runs within the Automox console, the steps to execute them for individual or bulk devices, and recommended usage.
Overview: Manual Execution Behavior
When you trigger a policy manually, the Automox agent bypasses its standard scheduled logic. It is important to understand the following behavioral changes:
Bypasses Evaluation: The policy runs immediately. It does not check the current "Pass/Fail" state of the device before attempting the installation.
No Notifications: End-user notifications (if configured) are suppressed during manual runs; the action begins the moment the command is received.
Immediate Remediation: The agent will attempt the installation and, if "Automatic Reboot" is enabled in the policy settings, the device will proceed to reboot after the task.
Pro Tip: Manual execution should be reserved for testing new policies or deploying critical, zero-day updates that cannot wait for the next scheduled sync.
How to Manually Run a Policy
Method 1: Individual Device
Use this method when you need to troubleshoot a single machine or verify a policy on a test seat.
Log into the Automox Console.
Navigate to the Devices tab.
Search for and click on the specific Device Name.
Scroll down to the Associated Policies section.
Click Run on this device next to the desired policy.
Monitor the Activity Logs to verify success or identify errors.
Method 2: Bulk Execution (Policy Level)
Use this method to push a policy to an entire group immediately.
Navigate to Automate > Policies.
Search for and select the policy you wish to run.
Click the Run Policy button at the top right.
Note on Reboots: Unlike Method 1, where reboot behavior can occasionally vary based on the individual device state, Method 2 is much more likely to trigger a reboot if "Automatic Reboot" is enabled in the policy.
Warning: This will trigger the policy on ALL devices currently assigned to the policy's groups, ignoring any specific device targeting or scheduling filters.
Best Practices & Automation
To maintain environmental health with minimal manual intervention, we recommend the following:
Verify Reboot Status: After running a policy manually via either method, always check the reboot status of the targeted devices. Since manual runs bypass standard notifications, users may be caught off guard by a restart, or a device may remain in a "Pending Reboot" state.
Shift to Schedules: Ideally, policies should be set to a recurring schedule to automate patching and ensure devices stay up-to-date without manual oversight.
Review Documentation: Follow the Automox Patching Best Practices Guide for templates on creating foundational policies.
Test Before Scaling: Always use the "Individual Device Method" to test a new policy on a non-critical machine before using the "Bulk Method."