Lock Mobile Device
Workflow #0047
Response Workflow
This workflow locks a Jamf-managed mobile device. Supported observables: mac_address
, hostname
, ip
Change Log
Date | Notes |
---|---|
Oct 11, 2021 | - Initial release |
Sep 7, 2022 | - Minor updates to naming and descriptions |
See the Important Notes page for more information about updating workflows
Requirements
- The following system atomics are used by this workflow:
- None
- The following atomic actions must be imported before you can import this workflow:
- Jamf Pro - Mobile Device - Execute Command (CiscoSecurity_Atomics)
- Jamf Pro - Mobile Device - Search (CiscoSecurity_Atomics)
- The targets and account keys listed at the bottom of the page
- Jamf Pro
Workflow Steps
- Make sure the observable is supported
- Search for a matching mobile device in Jamf
- Extract the mobile device’s ID
- If extraction was successful, execute the command on the device
Configuration
- Set the
Lock Message
local variable to the message to display on the locked device - If you want to change the name of this workflow in the pivot menu, change its display name
Targets
Target Group: Default TargetGroup
Target Name | Type | Details | Account Keys | Notes |
---|---|---|---|---|
Jamf Pro | HTTP Endpoint | Protocol: HTTPS Host: your-instance.jamfcloud.com Port: 443 Path: None | Jamf Pro Credentials |
Account Keys
Account Key Name | Type | Details | Notes |
---|---|---|---|
Jamf Pro Credentials | HTTP Basic Authentication | Username: Jamf API Username Password: Jamf API Password | Must have correct permissions depending on actions being performed |