Hey!

this is a fun one as there are quite a few ways to do it. 

which is another way of saying that there isn’t a super easy way to do it either. Haha

(easy note for our product team to take) 

do these servers all have the automox agent on them? 
or are you trying to orchestrate commands onto multiple servers from a central node?

Hint hint product. A lot of us would love to see a feature very similar to Orchestration Groups in SCCM. https://learn.microsoft.com/en-us/mem/configmgr/sum/deploy-use/orchestration-groups that give the ability to

• Run pre/post scripts with patching policy
• Install patches on group of devices based on
  • Specific Number at a time
  • Specific Percentage at a time
  • Explicit Order 

If you told me to create this solution on my own right now, I’d likely use the API to conduct my own orchestration. I’ve not used it, but perhaps Power Automate could make it a bit cleaner. Version one would be pretty generic, perhaps using a scheduled task on an internal windows system to run every 15 minutes pulling data from Automox and the Devices internally to validate state. 

workflow I’d likely follow

The first few runs would be very hands-on manual- with me releasing the push each time, but I think with enough scripting this could work….

• Query all endpoints. Save off the Device IDs for the specific systems in question
• Every 15 minutes pull status for each device in question https://developer.automox.com/openapi/axconsole/operation/getServer/
  • Validate Pending Reboot State
  • Issue command to reboot if pending a reboot https://developer.automox.com/openapi/axconsole/operation/issueDeviceCommand/ this is where I’d go to figure out how to issue device level commands, like Reboot.
  • Update a master record that both controls and tracks reboot order. This logic will require the most script work. Go basic at first, could use a file or all sorts of different things