Managing the OpenFrame Client — Updates & Recovery
Phase 10 — Ongoing Operations · OpenFrame Onboarding
The OpenFrame client on each endpoint isn't one program — it's a small bundle of agents (Fleet, MeshCentral, Tactical) coordinated by an updater service. Most of the time it looks after itself. This guide shows you how to confirm it's healthy, read its versions, and what "recovery" means when it isn't.
Where to check client health
Open a device from Devices, then the Agents tab on its detail page. You'll see a card for each underlying agent:
- Fleet — osquery-based inventory and monitoring.
- MeshCentral — remote control and file transfer.
- Tactical — RMM agent for scripts and actions.
Each card shows the same vital signs: Status (online/offline), Last seen, ID, Version, and Last fetched. A healthy client has all three online with recent "last seen" times.
Reading versions
The Version on each card tells you what's running on that endpoint. The OpenFrame updater service keeps these current automatically — it checks in, pulls the right versions, and applies them without you touching the machine. If one device is several versions behind its peers, that's a signal its updater isn't completing (often the same root cause as a disconnect — see the next guide).
You don't push client updates per-device by hand. The model is: the updater service on each endpoint pulls what it needs. Your job is to notice when a device falls behind, not to update it manually.
What "recovery" means
The OpenFrame client is designed to recover itself:
- On Windows, the client runs as a service registered with the Service Control Manager (SCM), which is configured to restart it automatically if it crashes or stops. That's the first line of defense — a hung agent usually comes back on its own.
- The updater service also repairs a partial or corrupted agent install by re-fetching the correct version on its next cycle.
So "recovery" is mostly automatic. When it isn't — the service is disabled, the host is off, or the network is blocking it — recovery happens on the endpoint, not from the console. The OpenFrame web console can show you status and versions, but the fix (restart the service, check connectivity, reinstall the agent) is done on the machine itself.
When a card shows offline
If one or all agent cards show OFFLINE with an old Last seen, the client isn't reaching the server. That's a disconnected-device situation — head to Troubleshooting a Disconnected Device (next) for the step-by-step.
Quick checklist
- Opened the device's Agents tab
- Confirmed Fleet / MeshCentral / Tactical are online with recent Last seen
- Checked Version on each card against your fleet's norm
- Understood updates are automatic via the updater service
- Knew recovery (SCM restart / reinstall) happens on the endpoint
What's next
When the client can't recover on its own and a device goes dark, work through Troubleshooting a Disconnected Device.
Based on OpenFrame v0.9.19. Agent components, versions, and the updater behavior evolve between releases — what's on the endpoint and in your console wins.
