Maintenance Items are scheduled tasks that run automatically on your devices — daily, weekly, or monthly — to keep them up to spec. They're a proactive way to run scripts across your fleet without manually touching each device.
Overview
A Maintenance Item runs a custom or saved script on a recurring schedule. Once created, you deploy it to devices the same way you deploy any other Catalog item: through a Policy.
How to Create a Maintenance Item
- Select Catalog on the navigation bar.
- Select the Maintenance tab in the Catalog section.
- Click New.
Configuration Options
The Create Maintenance modal includes the following settings:
- Name — the name that appears in your Catalog and Policies.
- Description — extra details you may want to add.
- Custom Script or Use Saved Script — enter a script directly, or choose one or more existing scripts created under Devices > Manage.
- Frequency — Daily, Weekly, or Monthly; the schedule on which the item runs.
-
Prompt User — when enabled, the end user sees a prompt before the item runs and can choose to proceed or cancel it.
-
Days before forcing without prompt — only available when Prompt User is checked and Frequency is Weekly or Monthly. Sets how many attempts occur before the item runs automatically without prompting the user.
-
- Use the device's local time for scheduling maintenance items — triggers the maintenance job based on the device's own time zone rather than a fixed time.
- Script Run Execution Time Out — the maximum time a maintenance item is allowed to run. If exceeded, the job is canceled.
- Time / Money Savings — enter Job time in minutes to calculate engineer time saved, based on your organization's EBA global setting.
Note: If a device is offline when a maintenance job is scheduled to run, the job reschedules for the same time the next day and counts as one failed attempt — this applies to weekly and monthly items as well. If a user declines a maintenance prompt, that also counts as a failed attempt. When a maintenance item is forced, an email summary of the forced jobs is sent. Click Save once you're happy with the settings.
How to Deploy a Maintenance Item
The new item appears in your Maintenance catalog. To run it on devices, follow Configuring and Deploying a Policy.
When Do Maintenance Items Run?
Maintenance items run at an arbitrary time within the scheduled hour, not at the exact minute selected. For example, an item scheduled for 7:00 AM might run at 7:00 AM on one device and 7:30 AM on another.
Technical Details: Maintenance Binaries
Maintenance items run through the maintenance-scheduler binary located at:
/Library/Addigy/maintenance-scheduler
Code requirement:
identifier "maintenance-scheduler" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = R5LEJ8Y242
Frequently Asked Questions
What happens if a device is offline when its maintenance job is scheduled?
The job reschedules for the same time the next day and counts as one failed attempt.
What if a user declines the maintenance prompt?
It counts as a failed attempt. If Days before forcing without prompt is set, the item will eventually run automatically once that threshold is reached.
Will a maintenance item run at the exact time I scheduled?
No — it runs sometime within that scheduled hour, and the exact minute can vary by device.