Pharaoh PHARAOH

REMOTE KVM

Reach machines when software access fails.

When the OS path, endpoint agent, RMM, or remote-control stack is unavailable, Pharaoh Remote KVM gives admins an out-of-band live screen and control path. Reduce outage duration, confirm what is happening, and avoid unnecessary truck rolls.

  • Hardware fallback A hardware KVM route stays available when normal endpoint software is not.
  • Outage time reduced Remote teams can investigate recovery flows before dispatching a technician.
  • Truck rolls avoided A live screen gives remote teams more evidence before sending someone on-site.
Scope a Pilot Explore KVM setup
Live screen published Target reachable Hardware path

WHERE IT HELPS

Built for break-glass endpoint recovery and remote-site resilience.

Remote KVM is the fallback path when the machine still matters but software access is down, degraded, or not trustworthy enough to use alone.

In plain English Remote KVM is a physical fallback path for IT teams when normal remote software cannot reach a machine.

Use this when

  • The endpoint agent is unreachable and normal remote access or RMM cannot help.
  • A machine is stuck before login, in a recovery flow, or otherwise outside the usual software path at a site you still need to support.
  • A lab, kiosk, remote office, or business-critical device needs durable access with session history and stale-state warnings before a truck roll.

Control model

Remote KVM adds durable access without bypassing Pharaoh approvals, session records, or stale-state warnings.

Out-of-band path
An Android-hosted KVM device acts as the recovery path to the target machine when OS-level tools fail.
No rules bypass
Starting a KVM session still requires the selected approval rules.
Operational truth
The session calls out offline runtimes and stale or missing screens before admins rely on evidence for recovery decisions.

HOW IT WORKS

Discover, manage, monitor - with approval still attached.

Remote KVM is its own product area, but it shares the approval rules, reusable instructions, and worklog model that admins and technicians already know from endpoint sessions.

  1. 01

    Discover

    Find the right KVM device in the inventory by name, status, or label — the list keeps Last Seen visible so stale devices surface fast.

    Inventory · status · labels
  2. 02

    Manage

    Open the detail page to confirm device identity, rename, update labels, and pick the approval rules that control the session.

    Labels · approval rules
  3. 03

    Monitor

    Watch the live KVM screen, send approval-checked requests, and load Playbooks — with explicit messaging when the Android runtime is offline or stale.

    Live screen · stale-state aware

INVENTORY

Find the right device before software paths come back

Remote KVM inventory is your starting point when normal endpoint paths are unavailable. Search, filter by status or label, and sort by Last Seen, Name, Status, Device type, or Associated endpoint to pick a device with confidence.

  • Search by display name or stable device id
  • Filter by Status and Label, sort the visible page by what matters most
  • Compact rows show display name, status, labels, and Last Seen
  • Empty states keep filters in place instead of resetting them
Remote KVM inventory with a seeded recovery KVM record visible

DEVICE DETAIL

Authoritative management for one KVM device

The detail page is the single management surface per device. Rename, update labels, and choose between Start session and Open session — the page tells the truth about current session state instead of forcing an extra click to find out.

  • Header shows display name, stable device id, and current online status
  • Rename through Display name with inline duplicate-name protection
  • Label autocomplete plus new custom labels keep inventory organized
  • Recent sessions stay visible so prior history is one click away
Remote KVM detail management page with labels and session launch controls

SESSION WORKSPACE

Live monitoring that tells the truth about connection state

The Remote KVM session workspace pairs a live screen with a shared transcript and session controls. When the Android runtime is offline, when no screen has been published yet, or when the latest screen is stale, the workspace stays usable and warns explicitly instead of pretending everything is fine.

  • Live screen monitoring next to the embedded worklog
  • Load Playbook reuses the same picker as other web composers
  • Send request, Stop work, and Close session controls
  • Stale-state messaging surfaces offline runtime, stale screens, or missing screens
Remote KVM session workspace with live screen monitoring

Resilient

Remote KVM keeps a path to the device when normal endpoint software paths are unavailable.

Truthful

Offline runtimes, stale screens, and missing screens are surfaced explicitly rather than hidden by an optimistic UI.

Guarded

Sessions still require approval rules — Remote KVM does not bypass Pharaoh controls when conventional paths fail.

EVALUATE PHARAOH

Scope a governed remediation pilot.

Review the product, active controls, security review questions, integration priorities, and deployment fit across your internal environment or managed client fleet.