Set the timetable. Overseer keeps to it.
Deployments say what should be true. A schedule says when Overseer checks and puts it right. Detection can run during the day because it changes nothing; execution waits for the maintenance window you set, and restarts follow your restart policy.
Your timetable
A schedule runs recurring detection and maintenance for the computers it targets, at the times you choose.
Changes wait for windows
Scheduled work that changes a computer runs only inside a maintenance window. Detection changes nothing, so it can run in working hours.
Restarts by rule
The restart policy decides whether and when a scheduled session may restart a computer.
Offline computers catch up
A computer that is switched off when its schedule comes round is not skipped. It catches up when it reconnects.
Maintenance without a timetable depends on memory.
- Work that runs when rememberedUpdates and clean-up happen when somebody has a free afternoon, so some computers go a long time without either.
- Changes at the wrong momentAn update restarts a computer in the middle of somebody’s working day.
- Timetables that do not line upPatching has one calendar and software updates another. The two collide, or leave gaps.
- The laptop that was switched offA computer that misses its slot is passed over, and nobody goes back for it.
One schedule covers detection, maintenance and restarts.
- Whole sessions, not single jobsA schedule starts a full maintenance session, which works out what each computer needs. You do not build a job per application.
- A rhythm for each clientAim a schedule at one client, a tag or every client, so each gets maintenance at the times that suit it.
- A small group firstTag a few computers and schedule them ahead of the rest. Review their sessions before the wider run.
- Saving changes nothingA new deployment does nothing by itself. It takes effect at the next session, scheduled or started by a person.
Three settings. Then it repeats.
Choose the work
Press New schedule and choose recurring detection, maintenance or both.
Choose the computers
Aim the schedule at every client, one client, a tag or a single computer.
Choose the timing
Set how often it runs, the maintenance window it keeps to and the restart policy.
Detection by day. Changes in the window.
| Work | Changes the computer | When it may run |
|---|---|---|
| Scheduled detection | No. It only reads | Any time, including working hours |
| Scheduled maintenance | Yes, where the computer differs | Inside the maintenance window |
| Restarts in a scheduled session | Yes | As the restart policy allows |
| Run maintenance, pressed by a person | Yes, where the computer differs | Immediately, whether or not a window is open |
Then leave it running.
Each time the schedule comes round, Overseer starts a session for every computer it targets, verifies the result and records the outcome. A computer that was offline catches up when it returns.
In development. Launch inquiries welcome.
Overseer is still being built and is not available yet. If you would like to hear when it launches, get in touch.