Skip to main content

Script Automation

Script Automation runs a script from your Script Library on a schedule you choose, on every endpoint that carries the tags you assign. It also powers Run Script on the Endpoints page and script remediation for Endpoint Checks.

Create an automation​

Open Orchestration > Script Library, select the Automations tab, then select New Automation. Give it a name, choose an approved script, enter its parameter values, choose at least one trigger, and assign tags. The automation runs on endpoints of the script's platform that carry those tags. The script's approved version runs; when a newer version is approved, endpoints receive it with their next automation update.

Triggers run independently. Choose At startup, At user login, On an interval, At a time of day, or Run once at. Startup runs once after each boot, and login runs once per login session. Intervals can be set from 15 minutes to 24 hours. A time-of-day trigger lets you choose days, a time, endpoint local time or a fixed time zone, and what to do when an endpoint is off. A one-time trigger runs at the date and time you choose. A script that runs as Logged-in user cannot use an At startup trigger because no user session exists at boot.

For a script that runs as Logged-in user, choose Local session only or All active sessions (including RDP). The latter runs once per session up to the session cap, which can be set from 1 to 10. Sessions above the cap are skipped.

A tenant can have up to 200 automations. Select Save Changes to save. If your tenant requires approval for automation changes, changes to the script, parameters, targets, or run-as options wait for a different administrator to approve them. Name, description, triggers, the Enabled switch, and safety settings save immediately. An automation awaiting approval continues using its current approved configuration. Linking a remediation script to a check policy is also subject to this setting.

Review endpoint results​

Open an automation to see the endpoints in scope. For each endpoint, results show its status, last run, and, when the endpoint has reported a current schedule, its next run. Consecutive failures are shown. Expand an endpoint to inspect its most recent run and output, if your permissions allow it.

An automation can pause on an endpoint after the configured number of consecutive failures. In the automation editor, set Pause after consecutive failures to choose the threshold. Set it to 0 to disable this pause. Paused endpoints show a Paused status and can be resumed from the endpoint's row in the automation results. An expired automation set or an outdated agent may also stop runs; the results identify those states.

Run a script once​

To run an approved script once, open Orchestration > Script Library and select the Scripts tab. Open the script's Actions menu and select Run.... Choose endpoints on the script's platform, enter parameter values, then select Run on [number] endpoints. You can also select endpoints in the Endpoints list and choose Run Script. The batch results show progress and per-endpoint outcomes; the runs are available under Run History.

Open a check policy under Orchestration > Endpoint Checks. In its Remediation section, enable Remediate failures with a script, choose an approved script and its parameters, select a mode, set the cooldown, and choose whether to Re-run the checks after the script finishes. Select Save remediation. For details about the two modes and safety behavior, see Run a Script When a Check Fails.

Script approval settings​

An administrator can manage approval in Settings > Sign-on Settings, under Script approval. Turn on Require a second administrator to approve script versions before they can run to require a different administrator with the Approve Scripts permission to approve versions. Turn on Also require approval for automation changes (script, parameters, targets, run-as) to require approval for those automation changes and for linking remediation scripts. Enabling, disabling, pausing, and resuming automations do not wait for approval.

Stop or pause scripts​

To stop one queued or running script, open its row in Run History and select Halt script. The run records whether the endpoint confirmed that the script stopped or the script ended before the halt arrived.

To stop an automation on every endpoint, disable it. To pause every automation in the tenant, select Pause all on the Automations tab. While all automations are paused, no new runs are dispatched. Queued and running runs continue unless you also select Cancel all running in the pause banner. Select Resume automations to start automations again. An automation paused on one endpoint after consecutive failures can be resumed from that endpoint's row in the automation results.

Offline endpoints receive changes when they reconnect. An offline endpoint stops using a disabled or removed automation at the lease boundary, no later than 7 days.

Account verification​

Custom Scripts require a verified account. New and free accounts cannot create, publish, approve, or run scripts, or use Script Automation, until verified. Paying an invoice verifies the account; having a card on file alone does not. You can also contact TridentStack support. A refunded, disputed, or returned payment removes verification associated with that payment. Existing accounts with active endpoints are already verified.