Script Runner setup

Set up SSP Script Runner so Jamf-style testing feels less like guesswork and more like a normal part of script work.

What this helps with

A scripting workspace where parameters, output, errors, and risky assumptions are visible before production Macs are involved.

Follow these steps.

1. Open the script you want to test and check what Jamf parameters it expects.
2. Add the values Jamf would normally pass at runtime.
3. Run the script once with normal values and once with an awkward or missing value.
4. Review stdout, stderr, exit code, and the guidance before changing anything in Jamf.
5. Save the script notes so the next admin can understand what was tested.

Checks before you move on

• Runtime parameters are named
• Output and errors reviewed
• Exit behaviour understood
• Notes saved with the script

Related guides

• Jamf parameter testing
• Enterprise Simulation
• Policy-safe script changes