OpenFrame

Remote Control Overview

GUIDEIT OPERATIONSOPENFRAMEREMOTE ACCESS

Phase 7 — Remote Access · Step 1

Section

June 23, 2026

Published

Vladislav Marchenko

Vladislav Marchenko

Head Of Marketing

Remote Control Overview

Phase 7 — Remote Access · OpenFrame Onboarding

Sometimes you just need to be on the machine — see the screen, move the mouse, fix the thing. OpenFrame's Remote Control gives you a full remote desktop session right in your browser, no separate client to install. This guide covers when to use it, how to start a session, and the controls you get once you're in.

When to use it

Remote Control is for hands-on, see-the-screen work: walking a user through something, fixing a GUI app, checking what's actually on screen. For quick command-line work, the Remote Shell is faster (see Using the Remote Shell); for moving files, use the File Manager (see Using the File Manager). Reach for Remote Control when you need eyes on the desktop.

Online vs. offline — the one prerequisite

The device has to be ONLINE. Remote Control connects live to the machine, so if a device shows OFFLINE, the remote actions are unavailable (greyed out). Check the device's status badge first — green ONLINE means you're good. If it's offline, you'll need to get it back on the network (or wake it) before you can connect.

Starting a session

  1. Open the device from the Devices list (or jump in from a ticket's "…" menu, Phase 6).
  2. On the device detail page, click Remote Control (top right).
  3. You'll land on the remote desktop view — it shows "Connecting to desktop…" and then the live screen appears.

That's it. You're looking at the actual machine.

The session controls

Across the top of the remote view:

  • Settings (gear) — tune the session: Quality (e.g. Balanced 50%), Scaling, Frame Rate (e.g. Medium 10 FPS), plus Invert Scroll Direction, Swap Mouse Buttons, and Use Remote Keyboard Map. Drop the quality/frame rate on a slow connection; raise them when you need detail.
  • Fullscreen (expand) — go full-screen for a roomier view.
  • "…" menu — the session toolbox:
    • Apply Shortcut — send key combos your browser would otherwise eat (Alt+Ctrl+Del, Win+L, Win+R, etc.).
    • Wake up / Sleep / Reboot / Shut Down — power actions on the remote machine.
    • Enable Input — toggle whether your keyboard/mouse actually control the remote.
    • Clipboard Sharing — share copy/paste between your machine and the remote.

The input and clipboard pieces have their own quirks worth knowing — see Clipboard & Input Sharing During Remote Sessions.

Quick checklist

  • Confirmed the device is ONLINE
  • Opened the device and clicked Remote Control
  • Waited for "Connecting to desktop…" to resolve into the live screen
  • Adjusted Quality / Frame Rate to match your connection
  • Know where the "…" menu (shortcuts, power, input, clipboard) lives

What's next

For command-line work instead of the full desktop, see Using the Remote Shell. To move files to or from the machine, see Using the File Manager. And for the copy-paste and keyboard gotchas, see Clipboard & Input Sharing During Remote Sessions.

Based on OpenFrame v0.9.19. Remote Control requires an online device and is actively evolving — what's in your console wins.

Vladislav Marchenko

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 7 — Remote Access

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.

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.
Most platforms give you one piece and expect you to bolt the rest on. OpenFrame unifies the whole stack in one place, with AI copilots built in. Fewer logins, fewer bills, less duct tape.
Both. It's built for MSPs and MSSPs alike.

AI for MSPs

AIOps, or AI for IT operations, applies machine learning to monitoring data to correlate alerts and predict failures before downtime hits. Industry figures put the impact at roughly a 30% reduction in downtime and up to 50% faster ticket resolution.

AI Infrastructure

Auto-remediation means the platform executes known fixes itself, like restarting hung services, clearing temp files, or retrying failed backups, then logs and documents the action. It typically covers the predictable majority of level-one infrastructure issues while escalating anything requiring judgment.

RMM Automation

The orchestration layer enriches the alert with device, site, and recent history, then picks one of three paths: self-heal a known issue, escalate, or open a ticket. A ticket is created only when judgment or a human touch is required.

Log Aggregation

Loki collects logs from many systems into one place, storing them cheaply by indexing labels instead of full content. You query them with LogQL inside Grafana. It is built to scale across hosts and clients while keeping storage costs low.