Skip to content
gaporo
Open app
Open app

Automation and scripts

How to run a script on a device, use the SaaS library, and when to open a ticket instead.

Automation module

Section titled “Automation module”

RMM → Automation shows tenant scripts (yours), the SaaS library (ready templates) and run history. Use it for repeatable fixes without logging onto every PC.

  • Tenant scripts — your company library.
  • SaaS library — ready scripts to clone / run.
  • Runs — status, stdout/stderr, exit code.

Safe System Disk Cleanup from the library runs even when plenty of free space remains. It clears temp (Windows and user profiles), browser cache without cookies or history, the Recycle Bin, and the Windows Update download cache. It does not touch the registry. $Mode = 'LowDisk' at the top of the script skips the work when free space is already high enough. The summary counts space used on disk, not the logical size of sparse files. A program started from the temp folder being cleaned is stopped. A program installed elsewhere that merely holds a file is left running and that file is skipped. Library script logs follow the Windows UI language (Polish or English).

Run a script step by step

Section titled “Run a script step by step”

Pick a script, choose a device (must be online), run and wait for the result. Cancel also stops a script that is already running (Windows agent 1.0.323 or newer, Linux agent 1.16.13 or newer). On older agents cancel only works before the script starts — a script already in flight runs to completion.

  1. Open Automation or the script action from the device card.
  2. Pick a device (must be online) — the script list filters by OS: Windows → PowerShell/CMD, Linux → Bash/Shell. Without a host the list stays empty on purpose.
  3. Select a script (tenant or SaaS library) and run.
  4. Check run history (exit code 0 usually means success). A library script is labelled “Library” in the selector.
  • Test on one PC first, then bulk.
  • System-changing scripts should run inside a maintenance window when you have one.

Script vs Service Desk ticket

Section titled “Script vs Service Desk ticket”

Script = fast, repeatable action. Ticket = tracked work with history for the team and customer. For a customer incident you often want: ticket (and CRM case) + script as the fix tool.

  • Disk cleanup / service restart on 20 PCs → Automation.
  • Outage for a customer with SLA → Service Desk + optional CRM case.
  • Do not close a ticket on script alone without verifying the device.
Section titled “Related”