Policy-safe script changes

Before editing a script, check where it is linked and what kind of Macs may be waiting for it.

What this helps with

A script change that keeps policy context visible instead of editing blind and hoping the scope is harmless.

Follow these steps.

1. Open the script and review linked policies before making changes.
2. Check trigger, frequency, scope, and any parameter values used by those policies.
3. Duplicate or stage the script if the current version is already doing live work.
4. Run the changed version through Script Runner with the policy values.
5. Write a short note explaining why the change is ready.

Checks before you move on

• Linked policies reviewed
• Scope understood
• Test run matches policy values
• Change reason documented

Related guides

• Script Runner setup
• Jamf parameter testing
• Enterprise Simulation