Repository navigation
Broadcast Command
Send one MDM command to devices on several Jamf Pro servers at once. ✏️ Sends commands to devices.
Use it when you run more than one Jamf Pro server and want to send the same command to devices on each of them in one go, for example a Blank Push to test Macs on your production and test servers.
Broadcast Command uses your Saved Servers. There's no Connect step: add the servers you want to target under Saved Servers → Manage Servers… first.
- Choose a Device Type: Mac computers or mobile devices. Changing it clears any devices you've picked.
- Choose a Command. The description underneath says what it does. If the command needs more details, fields appear for them: a PIN (required for Lock Computer and Wipe Computer, optional for Lock Device and Wipe Device), a Lock Message, a Lost Mode Phone Number, or a value such as a time zone (for example
America/New_York) or software version (for example17.5). Review & Send → stays unavailable until a required PIN (6 digits) or value is filled in. - Under Target Servers & Devices, tick each saved server to send to. A search box opens under it:
- Type a device name or serial number. Matches from that server are listed as you type.
- Click a match to add it, and click it again (or the ✕ under Selected devices) to remove it. The server's row shows how many devices are selected.
- Click Review & Send →. It's available once at least one ticked server has a device selected. The review screen shows the command, the number of servers and devices, and the devices for each server (the first 8, then …and N more).
- Click Send to All Servers. Every server is contacted at the same time.
Nothing is sent until you click Send to All Servers.
Broadcast Complete shows a card for each server with N/N succeeded, and a row for each serial number:
- Command queued: the command was queued for that device.
- An error message, if the command couldn't be sent.
If the app can't sign in to a server, its card says Authentication failed and why. New Broadcast starts again.
- Commands are sent exactly as Command sends them, through the Jamf Pro API or the Classic API as each command needs, so every command in the list works the same in both tools.
- Each server sends the command through its own credentials, so each saved server's account needs the right privileges.
Permissions (on each server): Read Computers or Read Mobile Devices (to search for devices), plus the Send … Command privilege for the command, under Jamf Pro Server Actions. There's no permission screen.
Magic Toolbox © MDM Magic · mdmmagic.au · Releases · Report an issue
Getting started
Deployment
Jamf Pro Tools
- Clone
- Compare
- Wipe
- Restore
- Disable
- Create
- Command
- Broadcast Command
- Device Logs
- LAPS
- MDM Command Queue
- Redeploy
- Webhook Manager
- Self Service Descriptions
Audit & Health Check
- Profile Conflicts
- Smart Group Audit
- Account Audit
- Cert & Token Expiry
- Unused
- Network Check
- Script Auditor
- Fleet Health
- Extension Attributes
- Self Service Audit
- Stale Devices
- Profile Drift
- Policy Audit
- Patch Compliance
- Conditional Access
- Category Audit
- Pre-stage Audit
- Enrolment Funnel
Profile Builders
- PPPC Analyser
- System Extensions
- Web Content Filter
- Notifications
- Login Item Profiles
- Profile Signer
- Profile Unsigner
- Profile Inspector
- Uploading Profiles
Content & Packages
Reference