Run Script lets you execute one or more saved scripts on a managed device, straight from the Device Details page. It's the fastest way to push a remediation, diagnostic, or maintenance task to a single device without opening a remote session.
This guide covers how to launch the script runner, pick scripts, run them, and find the results.
Where to find it
- Open Devices in the left nav and select the target device.
- On the device's detail page, click the … (more actions) button at the top right of the header.
- Choose Run Script from the menu (the ↗ icon means it opens the script picker).
The device has to be ONLINE with a healthy agent for scripts to run. Check the Agents tab if Run Script results never show up.
The "Select Script" dialog
Clicking Run Script opens the Select Script modal — "Choose scripts to execute on this device."
Finding a script
- Search for Script — a search box at the top. Type any part of a script's name to filter the list (e.g. typing speed surfaces Network – Speed Test, Speed Test – Powershell, and Test Network Speed). Search matches the script title.
- Category filters — chips below the search box (e.g. Deprecated, Monitoring, OpenFrame) narrow the list to a category. Show All clears the category filter and brings back the full library.
- If nothing matches, the dialog shows "No scripts found matching your criteria" — broaden the term or clear the filters.
Tip: search is exact-ish on the title. If a name doesn't match (e.g. "Speedtest" as one word), try a shorter fragment ("speed").
Selecting scripts
- Each result is a card with the script name and a short description of what it does, plus a checkbox on the right.
- Tick one or more checkboxes to queue them — Run Script lets you select multiple scripts at once.
- Select All queues every script currently shown.
- A selected script is highlighted, and the action button becomes active (Run Script). With nothing selected, the button is disabled.
Choosing the right script for the platform
Scripts are often platform-specific — read the description before you run. For example, among the speed-test scripts:
| Script | Description | Best for |
|---|---|---|
| Network – Speed Test | Runs a speed test using Python | Devices with Python available |
| Speed Test – Powershell | Speed test with PowerShell (Win10 / Server 2016+) | Windows devices |
| Test Network Speed | Downloads and runs iperf; needs one machine as server and another as client | iperf-based throughput testing between two hosts |
On a Windows device, the PowerShell variant is the safe bet.
Running scripts
- Select the script(s).
- Click Run Script (bottom right). Cancel closes the dialog without running anything.
- The dialog closes and you're taken to the device's Logs tab, where execution results get reported.
There's no separate confirmation step after Run Script — clicking it dispatches the job immediately. Only select scripts you actually mean to run on the live device.
Viewing results
Script output lands on the device's Logs tab (you're taken there automatically after running). The log table has columns: Log ID, Status, Tool, Source, Log Details, with a Search for Logs box and column filters.
- Click Refresh to pull the latest entries.
- Results aren't instant — the agent has to run the script and report back, so a new entry can take anywhere from a few seconds to a few minutes to appear. Refresh every so often.
- Use the Status column to confirm success/failure and Log Details to read the output.
Common workflows
Quick diagnostic. … → Run Script → search for the diagnostic (e.g. Speed Test) → select → Run Script → watch the Logs tab and Refresh for output.
Batch maintenance. Open the picker, use a category filter (e.g. OpenFrame) or Select All, queue several scripts, and run them together.
Targeted remediation. Search for the specific fix script, confirm its description matches the device OS, run it, then verify the result in Logs.
Notes and tips
- Run Script targets this one device. For fleet-wide execution, use the Scripts section in the main nav.
- Always read the script description — many are OS-specific or have prerequisites (e.g. Test Network Speed needs a paired server/client).
- If results never show in Logs, the device or its agent may be offline — check the Agents tab.
- Scripts marked Deprecated may not work; prefer the current equivalents.
