OpenFrame is on your phone now!

Device Details Page: Overview

DEVICE MANAGEMENTDOCUMENTATIONENDPOINT MANAGEMENTGUIDEIT OPERATIONSOPENFRAME

Phase 3 — Platform Navigation · Step 4

Section

September 24, 2026

Published

Vladislav Marchenko

Vladislav Marchenko

Head Of Marketing

Reviewed 24/09/2026

The Device Details page is the single-device control center in OpenFrame. From here you can review a managed device's full inventory (hardware, network, users, software), check its security and compliance posture, inspect the agents reporting on it, run remote sessions and scripts, and manage the device's lifecycle.

This guide walks every section and action on the page, with notes on what each is for and when you'd reach for it.


Getting to the page

Open Devices in the left nav, then pick a device from the list. Each device has its own detail URL of the form:

ini
/devices/details/<device-uuid>/?tab=<tab-name>

The tab query parameter controls which tab is shown (e.g. ?tab=security), so you can deep-link or bookmark a specific tab for a device.

Use ← Back (top left) to return to the device list.


The header stays visible no matter which tab is open.

Device name and status. The device's display name (e.g. VM116194) appears as the page title, with a colored status badge below it (ONLINE / OFFLINE). Status reflects the most recent agent check-in.

Action buttons (top right):

  • Remote Control — launches a remote desktop session to the device (opens in a new window, marked by the ↗ icon). Use it for interactive, GUI-level support.
  • Remote Shell — opens a remote command-line session on the device. The adjacent dropdown (▾) lets you choose the shell/connection option before launching. Use it for scripted or terminal-based work.
  • … (more actions) — opens a menu with lifecycle actions (see below).

Remote Control and Remote Shell need the device online and the relevant agent (e.g. MeshCentral / RMM) connected. If they look unavailable, check the Agents tab.


The "…" actions menu

ActionWhat it doesNotes
Run ScriptOpens the script runner targeted at this device (↗).Use it to push a one-off or saved script to the device.
Edit Display NameSet the device friendly name, e.g. "Second Reception Machine"
Manage FilesRemote access to the devices file system. Supports functions: Download, Copy, Rename, Cut, Delete, Upload and New Folder
Reboot DeviceInitiates a remote reboot
Delete DevicePermanently removes the device.Destructive. Shown in red. Use with care; prefer Archive when unsure.

Device summary card

Right under the header is a summary card with the device's identity fields:

  • Hostname — the device's network hostname.
  • Type — device form factor (e.g. DESKTOP).
  • Device — manufacturer/model (e.g. Microsoft Corporation, Virtual Machine).
  • Serial Number — hardware serial.
  • Customer ID (Site) — the customer/site the device belongs to. This is a link to the site.
  • Registered — when the device was first enrolled.
  • Updated — timestamp of the most recent data refresh.
  • UUID — the device's unique identifier (also in the page URL).

Tabs

The detail view is organized into nine tabs: Hardware, Network, Security, Compliance, Agents, Users, Software, Vulnerabilities, Logs.

Hardware

Physical/virtual resource inventory.

  • Disk Info — one card per drive showing Current Usage (%), Used Space, Free Space, and Total Capacity, with a usage bar. Virtual/partition-less drives may show N/A for some fields.
  • Memory — Total Memory.
  • CPU — processor model, Physical Cores, Logical Cores, and architecture Type (e.g. x86_64).

Use this tab to verify capacity, plan upgrades, or chase down performance complaints.

Network

  • Public IP / IP Address — the device's internet-facing address.
  • Local IPv4 Addresses — internal interface addresses.

Use it to confirm connectivity details and reachability.

Security

The device's overall security posture, grouped into sections:

  • Encryption Status — Disk Encryption (Enabled/Disabled) and whether an Encryption Key is available.
  • Security Agents — versions/status of the OpenFrame Agent, osquery, and Orbit Agent.
  • Posture — Policy Compliance: Failing Policies and Total Issues.

Agents

Status of every management agent reporting on the device. For each agent (e.g. Fleet, MeshCentral, OpenFrame Client, Osquery, OpenFrame Chat) you'll see Status (ONLINE/OFFLINE), Last seen, ID, and Version where applicable.

This is the first tab to check when remote actions fail or data looks stale — an offline agent usually explains it.

Users

Account inventory for the device.

  • All System Users (N) — a card per local/domain account showing UID, Group, Shell, and Type (e.g. local).

Use it for security review (unexpected accounts, privileged group membership) and audit.

Software

A searchable, sortable inventory of installed software, with a count (e.g. Installed Software (33)) and columns:

  • Software (name + version)
  • Source (e.g. Windows, Chrome, IE, publisher signature)
  • Vulnerabilities (e.g. No Issues)
  • Last Used

Use the search box to find a specific app and the Security column to spot flagged items.

Vulnerabilities

Lists known vulnerabilities tied to installed software. When clean, it shows No Vulnerabilities Found — All installed software is up to date and secure. Otherwise it lists the affected software and severity.

Use it as the actionable companion to the Software tab for risk remediation.

Common administrator workflows

Onboard / verify a new device. Check the summary card (correct site, recent Updated time) → Agents tab to confirm all agents are ONLINE → Security tab to confirm encryption and alert settings.

Respond to a support request. Confirm ONLINE status → use Remote Control (GUI) or Remote Shell (CLI) → optionally Run Script from the "…" menu for a repeatable fix → review the Logs tab afterward.

Security / compliance review. Security tab (encryption, agents, sessions) → Compliance tab (patches, policies, checks) → Vulnerabilities tab → Users tab for account audit.

Retire a device. Use … → Archive Device to retire while keeping history; use … → Delete Device only for permanent removal.


Notes and tips

  • The page is read-mostly: most tabs show inventory and posture data refreshed from agents. The actionable controls are the header buttons (Remote Control, Remote Shell, "…" menu).
  • Data freshness depends on agent check-ins — see Updated in the summary card and Last seen per agent.
  • Deep-link straight to any tab via the ?tab= URL parameter.
  • Delete Device is destructive and can't be undone; prefer Archive unless permanent removal is the goal.
Vladislav Marchenko

Head Of Marketing

Hi all! My name is Vlad and I’ve been brought on to head the marketing team at Flamingo. Thankfully, this isn’t the first time I will be building a marketing department from scratch, so the experience should come in handy. Now it’s time to dive into the world of MSPs and find myself in this new world.

More in Phase 3 — Platform Navigation

Related Content

Product Releases

Webinars

Case Studies

Blog Posts

Frequently Asked Questions

MSP AI Agents

Yes. In production MSP shops today, 10% to 25% of tickets close before a human opens them. Thread alone has processed 173 million tickets across 750-plus MSP partners at 96% triage accuracy, handing back 490,000-plus technician hours. Agents own the low-risk, high-volume work (password resets, MFA enrollment, known installs, onboarding and offboarding) and flag anything that touches production data or needs judgment for a human to take.
On a five-person desk, reported deployments show $78,000 to $130,000 in annual direct labor savings, roughly 30% fewer escalations, and 15% to 20% better SLA compliance. Broader MSP adoption data adds ticket handling time cut by 45% and five to 12 points of margin, all from reclaimed capacity rather than headcount cuts.

AI MSP

Automate high-volume, low-risk tasks first. Ticket triage and alert noise reduction top the list because they run constantly and a human still resolves the underlying issue. Save security approvals, billing changes, and client-facing actions for later, always with a human in the loop.

Getting Started

The People Hub is Flamingo's internal home for the team. Every employee can browse the team roster, open a colleague's “Who Am I” profile, share what they shipped each month, and keep their own profile up to date. Managers additionally see performance insights built on the SPACE framework.

About OpenFrame

OpenFrame isn't built to plug into your stack. It replaces it. Instead of duct-taping a dozen tools together (RMM, MDM, SIEM, patching, remote access, each its own login and bill), we bundle it into one unified platform: RMM, MDM, monitoring, automation, remote access, patch management, security monitoring, and ticketing, plus built-in AI copilots. So "does it integrate with X?" usually means: you won't need X anymore.
Nine, per Ivanti's own End of Life index: Cherwell Service Management, Cherwell Asset Management, Service Desk (Powered by LANDESK), Desktop & Server Management, Endpoint Security (Powered by HEAT), PatchLink, Workspace Control, Virtual Desktop Extender and Browser Manager. DSM 2026.1 is the sharpest case, since it shipped on 13 January 2026 and loses full support in December of the same year.
Not since iOS 26, iPadOS 26 and macOS 26. Apple supports moving managed devices between management services without wiping, but only for devices enrolled through Automated Device Enrollment, and not for Shared iPad or devices configured for Return to Service with app preservation. Apps survive on iPhone and iPad only if the new service delivers them before the DeviceConfigured command. Apple also states that you need to re-create your enrollment profile and configurations in the new service.
No vendor documents an import path from Ivanti EPM. ManageEngine's migration-paths page, updated 26 August 2026, lists Ivanti DSM, Ivanti EPMM and Ivanti Neurons as supported sources and omits EPM. NinjaOne and Microsoft do not document one either. Patch policies, provisioning templates, LANDesk scripts, inventory history and custom fields get rebuilt rather than migrated.
It is the total power a switch can supply across all its ports, which is almost always less than ports times the per-port maximum. Add up the device draws at their IEEE class: 802.3af phones at 12.95 W, 802.3at access points and cameras at 25.5 W, 802.3bt devices at 51 W or 71.3 W. Add 20% headroom and buy a switch whose total budget exceeds that figure.
It means one screen that shows the state of everything a team manages: devices, tickets, alerts and users. In practice the phrase covers three different products: a dashboard that reads from your other tools, a suite of separate modules from one vendor, and a platform where every module shares one database.