You ran the installer. Now make sure OpenFrame actually sees the machine — and if it doesn't, know exactly where to look. This is a two-minute check that saves you from assuming a device is managed when it isn't.
The quick check
- Left nav → Devices.
- Find your machine in the list. You can search by name in the Search for Devices box if the list is long.
- Look at the Status column:
- Online (green) — it's connected and reporting. Done.
- Offline (red) — it enrolled but isn't currently checking in. See troubleshooting below.
Each row also shows the OS (macOS / Windows) and the Customer it's assigned to — a good moment to confirm the device landed under the right client.
The dashboard's Devices Overview also gives you an at-a-glance Online vs. Offline count, which is handy once you've got more than a handful enrolled.
Confirm it's really reporting
A device that's truly managed has live data behind it. Click the device name to open its detail page and confirm real information is flowing:
- Hostname, Type, Device model, and Serial Number are populated up top.
- The Updated timestamp is recent (it refreshes as the device checks in).
- The tabs — Hardware, Network, Security, Compliance, Agents, Users, Software, Vulnerabilities, Logs — show actual data. Hardware, for example, should list disks, RAM, CPU, and battery health.
If the detail page is full of real specs, you're genuinely managing that machine — not just looking at an enrollment record.
For an online device you'll also see Remote Control and Remote Shell available at the top right — proof the connection is live (covered in Phase 7).
If the device doesn't show up at all
Work down this list:
- Give it a minute. Enrollment-to-first-checkin isn't instant. Refresh the Devices list after 60–120 seconds.
- Right customer? If you're filtering by customer or only scanning one client's devices, the machine may have enrolled under a different customer. Clear filters and search by name.
- Did the installer actually finish? Re-check the install terminal/PowerShell output for errors. An AV block or a missing
sudo/elevation will stop registration. Re-run with the fixes in the macOS or Windows install guide. - AV quarantine. If antivirus ate the client mid-install, it never registered. Add the exclusions from the install guide and run it again.
If it shows up but is Offline
- Recently installed? First check-in can lag a couple of minutes. Wait and refresh.
- Is the machine on and awake? An offline status often just means the device is powered down, asleep, or off the network. The Last Seen time tells you when it last reported.
- Network path. A firewall, proxy, or content filter between the device and your tenant can block check-ins. Confirm the machine can reach your OpenFrame server URL.
- Agent health. If it's online, awake, and networked but still offline, the agent/service may need a nudge — see Managing the OpenFrame Client — Updates & Recovery and Troubleshooting a Disconnected Device (Phase 10) for agent logs, service restarts, and token rotation.
Quick checklist
- Device appears under Devices
- Status shows Online
- It's assigned to the correct customer
- Detail page shows real hardware/network data and a recent Updated time
- (If applicable) Worked through the troubleshooting steps for a missing or offline device
What's next
One device verified, the pattern proven. Now scale it: Deploy at Scale via RMM / GPO / MDM for mass rollout, then tidy your fleet with Add a Device Display Name / Nickname and Organize Devices with Device Tags.
Based on OpenFrame v0.9.19. Screens and defaults may shift between releases — when in doubt, what's in your console wins.
