Quarterly laptop refresh check automation

On the first day of each quarter, Risotto runs a script tool across every Mac in Iru, then opens one ticket with everyone due for a refresh. The ticket goes straight to the refresh runbook, which gets the approval and places the orders.

Book a demo See the library

The script tool it runs

The automation decides when to look and how old is too old: 3 years. The Iru laptop refresh script tool does the checking the same way every time. It reads every Mac in Iru, finds each person’s oldest one, and picks the replacement from your hardware standard by title and department. Run from here, it orders nothing.

The runbook it hands the ticket to

The ticket is locked to the Quarterly laptop refresh runbook, so no request matching is involved. The runbook gets one approval for the whole batch, runs the same script tool again with ordering on, then sends a Revivn box for each old Mac.

Frequently asked questions

What starts the quarterly laptop refresh check automation?

A schedule: the 1st of each quarter at 9:00 AM Pacific. You set the day and the time in the trigger, or run it monthly to catch Macs as they turn 3.

Why does the automation open the ticket, not the script tool?

A ticket needs a requester, and an automation run has none, so a script tool that opens a ticket from an automation run is refused. The automation’s own Create Ticket tool names one, here the IT lead, and locks the ticket to the runbook. The script tool just finds who’s due and returns the list.

Which steps in the quarterly laptop refresh check wait for approval?

It asks for approval on destructive changes, as the dashboard puts it: creates and updates run unless a tool requires approval, and deletes and revokes wait for an admin. Nothing here spends money: the script tool runs with ordering off, and the one change is the ticket it opens. The approval for the orders comes in the runbook, where the approver sees the whole list and the total.

How do I build the quarterly laptop refresh check in Risotto?

Describe it to Risotto’s Assistant: what starts it and what should happen. The Assistant builds the automation, the script tool and the runbook from the systems you’ve connected, and shows you each change before it saves.