Remote operations

Fix it from your desk,
with approvals built in.

Send diagnostics and safe fixes to your Windows PCs through their agent, hold the risky actions for a second administrator, and let self-healing answer your own alerts. It is not remote desktop: nothing takes over a screen.

  • In the Free and Enterprise plans
  • Free trial on every plan, no card needed

What it does

Remote operations, in detail

Diagnostics without a site visit

A system snapshot, running services, top processes, a ping and DNS test, pending updates or a fresh inventory, from several PCs at once. Read-only checks need no approval.

How it works: Diagnostics without a site visit

Approvals matched to the risk

Flushing DNS or restarting a service waits for one approval. Reboots, shutdowns and software installs need a second administrator, and whoever asked can't approve.

How it works: Approvals matched to the risk

Maintenance windows

Set a daily window and reboots, shutdowns and software installs can be approved only inside it. With no window set they are not time-restricted.

How it works: Maintenance windows

Software installs, hash-checked

Register an installer with its SHA-256 hash; each PC downloads it and refuses to install unless the hash matches. Installs and rollbacks need a second admin.

How it works: Software installs, hash-checked

Self-healing from your alerts

Link an alert type to one safe command and the PC the alert is about gets it. Only read-only or reversible commands qualify; reboots and installs never run on their own.

How it works: Self-healing from your alerts

Dry run first, with limits

New rules start in dry run and only log what they would have done. Live rules are limited per PC, 3 runs an hour and a 30-minute cooldown by default.

How it works: Dry run first, with limits

See which fixes worked

Each rule counts the fixes that succeeded, failed, expired or were skipped. If a fix fails, or the alert is still open 30 minutes later, the right people are told.

How it works: See which fixes worked

Results and a job history

Every PC's exit code and output, kept with the job. Search the history by command, status, risk or time; jobs no PC answered close as expired, with the reason.

Recorded in the audit log

Requests, approvals, refusals, automatic runs, results and changes to rules and the software list are written to your company's audit log.

How it works: Recorded in the audit log

Signed jobs from a fixed list

Each job is signed for one PC and carries a deadline. The agent runs only commands from its built-in list and refuses a bad signature or a passed deadline.

Getting started

Up and running in three steps

  1. Switch on remote managementAn administrator turns it on and can set a maintenance window for disruptive actions.
  2. Run your first commandPick a command and one or more PCs; medium- and high-risk commands wait for approval.
  3. Add self-healing rulesLink an alert to a safe command. Rules stay in dry run until you choose Go live.

Plans

Which plans include it

  • Remote operationsFreeEnterprise
  • Self-healing automationFreeEnterprise

Straight from the live plan catalogue, the same rules the product enforces. Compare plans and prices

Try remote operations on your own setup

Start a free trial, or book a demo and we will walk you through it.

Book a demo Free trial