RMM script execution that fixes endpoints without remoting in
Most endpoint tickets end with a tech remoting in: interrupt the user, click through startup items, run the fix by hand. Rallied reads the endpoint over your RMM, proposes the script that fixes it, and gets the plan on the ticket in minutes. Nothing runs until the ticket owner approves.
How it works
Your tech’s job changes from doing the fix to approving it. Everything Rallied checks and everything it wants to run is on the ticket.
- Find the endpoint.
- Matches the ticket to the right device in your RMM and confirms it is online, so it never proposes work against a dead machine.
- Diagnose from live state.
- Reads the active session, startup items, and past audits over the RMM. The user keeps working the whole time.
- Propose the script.
- Uses an existing script when one fits, and writes one when nothing does. The plan goes on the ticket as plain steps, and the ticket owner replies approved or denied.
- Run it and write back.
- On approval it runs the script and writes what changed into the ticket notes. If the owner denies it, the diagnosis still stays on the ticket.
We tracked 232 hours on printer tickets in a single month, and the fix is almost always the same: stop the spooler, clear the queue, start it back up. We rolled that out as a workflow with Rallied, and it resolved its first ticket the same day.
