Where to find it: in the Hub (your MSP workspace at app.theonestack.com), open RMM, then use the RMM sidebar or page links below:
- RMM → Automation → Scripts: app.theonestack.com/rmm/scripts
- RMM → Automation → Jobs: app.theonestack.com/rmm/jobs
- RMM → Devices → All Devices (pick a device): app.theonestack.com/rmm/devices
Overview
Remote Commands lets technicians run scripts and one-off commands on devices without opening an interactive terminal. Commands are queued, executed by the agent, and results are stored so you can review them later. You can target a single device or run the same command across many devices at once.
Running a Command on a Single Device
- Open the device from the Devices list.
- Click Run Script.
- Choose how to provide the command:
- Script library — pick a saved script from your organization's library.
- Community Scripts — browse scripts shared by other MSPs in the community.
- Ad-hoc — paste a PowerShell, Bash, or shell script directly.
- If the script has parameters, fill them in before running.
- Click Run. The command enters the queue immediately.
Tracking Command Status
After submitting a command, the status moves through these stages:
| Status | Meaning |
|---|---|
| Pending | Queued, waiting for the agent to pick it up. |
| Dispatched | Sent to the agent; execution in progress. |
| Complete | Finished. Output is available. |
| Failed | The agent ran the command but reported a non-zero exit code. |
If a device is offline when you submit, the command stays in Pending until the device comes back online and heartbeats. Commands are not lost.
Viewing Output
Click any completed run in the command history to open the run detail. The detail view shows:
- Standard output (stdout) — what the script printed.
- Standard error (stderr) — any error messages.
- Exit code — 0 typically means success.
- Duration — how long the command took.
Command History
All past runs for a device are listed on the device detail page under Script Runs. To see runs across all devices, go to Scripts in the top navigation and click Run History.
Running a Command on Multiple Devices
- Go to Scripts in the top navigation.
- Select the script you want to run.
- Click Run and choose Target Multiple Devices.
- Pick your targets by client, operating system, device group, or by selecting devices individually.
- Click Run. A bulk job is created and you can track per-device progress from the bulk job status page.
Each device gets its own command queued independently. Offline devices will execute when they come back online.
Frequently Asked Questions
A command has been in Pending for a long time. What is wrong?
The device is most likely offline. Check the device status. The command will run automatically when the device reconnects.
stdout is empty but the exit code is 0.
The script ran successfully but did not print any output. Review the script logic if you expected output.
Can I cancel a pending command?
Open the device detail, find the pending command in the run list, and delete it before the device picks it up. Once dispatched it cannot be cancelled.
How is the community script library different from my script library?
Community scripts are shared by MSPs across the platform and are read-only. You can import any community script into your own library and modify it from there.