How to Use RMM Scripts, Policies & Auto-Remediation

The three building blocks

Feature	What it does	Where
Script Library	Reusable PowerShell / Bash scripts you can run on demand or on a schedule	RMM → Scripts
Policies	Configuration standards enforced across a device group	RMM → Policies
Automations	Triggers that run a script automatically when a condition is met	RMM → Automations

Building the script library

1. Go to RMM → Scripts
2. Click + New Script
3. Choose the platform (Windows / macOS / Linux) and paste the script
4. Add parameters if the script needs input
5. Save — the script is now reusable across any device

Run a script on demand from a device's detail page, or attach it to an automation.

Creating a policy

1. Go to RMM → Policies
2. Click + New Policy
3. Define the desired state — for example:
   • Firewall enabled
   • Disk encryption on
   • A specific service running
4. Assign the policy to a device group
5. Plenix continuously checks compliance and flags (or remediates) any drift

Setting up auto-remediation

1. Go to RMM → Automations
2. Click + New Automation
3. Define:
   • Trigger — e.g. "Disk space below 10%" or "Policy drift detected"
   • Action — run a script from the library (e.g. clear temp files, restart a service)
   • Scope — a device or device group
4. Save. The next time the condition occurs, Plenix runs the fix automatically and logs it.

Example: self-healing disk cleanup

• Trigger: free disk space < 10%
• Action: run the "Cleanup Temp & Logs" script
• Scope: All Workstations
• Result: the disk is cleaned automatically; if it stays low, an alert and ticket are raised

Tips

• Test scripts on a single device before attaching them to a group-wide automation
• Every automated action is written to the audit trail
• Combine policies with patch policies for a complete "keep every device healthy" baseline

Where to go next

• Understand the whole module → How Remote Management (RMM) Works
• Next in this module → Install the Plenix Gateway Agent
• How to Remote Control a Managed Device
• See where this fits in the bigger picture → How a Device Problem Becomes a Fix