Reviewed 05/10/2026
Scripts Overview
Phase 5 — Scripts & Automation · OpenFrame Onboarding
Scripts are how you do things to machines at scale — install software, pull a report, fix a recurring problem — without remoting into each one by hand. In OpenFrame they live under Scripts in the left nav, and this section is split into two tabs: Scripts List (your library) and Scripts Schedules (scripts set to run on a cadence). This guide is the lay of the land before the next four go deep.
Scripts List
Open Scripts and you land on Scripts List — a table of every script available in your tenant. Select a script to view script details:
- Name — what the script does.
- Shell Type — the language it's written in (see below).
- OS — which platforms it can target (Windows, Linux, macOS icons).
- Category — how it's grouped, e.g. Diagnostics
- Run as User — Run in the user context
- Timeout — Time that the script will automatically terminate if not completed.
- Add script argument — Add a default argument
- Add Environment Var — Add an Environment Variable
- Add Secret — Add an encrypted key/password
Scripts Schedules
Select Scripts Schedules for an overview all your scheduled scripts. Select a script schedule to view details:
Edit Script Schedule
- Run on Schedule/Run when device comes online — The script will run at a set interval; or the very next time it comes online
- Supported Platform — Windows or MacOS
- Date — Effective start date
- Time — The time to run the script
- Timezone — Script can be set to run at the client local time, or the OpenFrame user local time
- Repeat Script Run — Specify how often the script should run, each minute, hour, day, week, month
- If device is offline at scheduled time — Select to either skip run or run the script when the machine is next online
Scheduled Scripts
- Scheduled Script — Select the script you want to run
- Timeout — Amount of time the script will run before timing out automatically.
- Script Arguments — Runtime arguments to pass to script
- Add script argument — Add a default argument
- Add Environment Var — Add an Environment Variable
- Add Secret — Add an encrypted key/password
Use Search for Scripts to filter, and the column header sort/filter controls to narrow by shell type or OS. Each row has a "…" menu and an arrow button that opens the script's detail page.
Supported shell types
OpenFrame runs more than just PowerShell. When you create a script you pick from:
- PowerShell — the workhorse for Windows.
- Batch — classic Windows
.bat. - Bash — Linux and macOS.
A script declares which OS it supports, so the library only offers a script to machines it can actually run on.
Two ways scripts run
- On demand — run a script against one or more devices right now. You can do this from the script's detail page (Run Script) or from a device's own page. Covered in Run a Script on a Device.
- On a schedule — set a script to run at a date/time, optionally repeating. That's the Scripts Schedules tab, covered in Schedule a Script.
Either way, results land in the Logs (activity logs) — see Script Results & Output Logs.
What's in a script
Click any script's arrow to open its detail page:
- Description and Category — what it is and how it's filed.
- Shell Type and Supported Platforms — language and target OSes.
- Syntax — the actual code, shown read-only.
- Edit Script and Run Script — buttons to change it or run it now.
Quick checklist
- Found the Scripts section and the Scripts List / Scripts Schedules tabs
- Scanned the library by Category and OS
- Understood the supported shell types
- Know the difference between running on demand vs on a schedule
- Know where to find a script's Syntax and the Run Script button
What's next
Now that you know where scripts live, put one to work: Run a Script on a Device covers running on demand (and the variable gotcha between running from /scripts and from a device). Then Create Your First Script and Schedule a Script.
Based on OpenFrame v0.9.19. Screens and the bundled script library evolve between releases — when in doubt, what's in your console wins.
