.png){kind=logo}
Jamf Pro - Lock Device
- 30 Dec 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Jamf Pro - Lock Device
- Updated on 30 Dec 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Jamf Pro - Lock Device locks the user's device for:
- Assets returned by the selected query or assets selected on the relevant asset page.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
Note:
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
Required Fields
These fields must be configured to run the Enforcement Set.
- Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
Use stored credentials from the Jamf Pro adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.
- When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.
Note:To use this option, you must successfully configure a Jamf Pro adapter connection.Passcode - The code pre-configured in Jamf to confirm the requester can run the “lock device” command.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
Connection and Credentials
When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.
- Jamf Domain - The hostname of the Jamf Pro server. This field format is 'https://[instance].jamfcloud.com'.
- User Name and Password - The credentials for a user account that has the permissions to perform this Enforcement Action.
- HTTP Proxy and HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
- HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.
- Tenant Tag (optional) - Specify a tag name.
- Bypass SSO - Switch on if SSO is enabled and the created user account should be logged directly to Jamf Pro.
- 2FA Secret Key (optional) - The secret generated in Jamf Pro for setting up 2-factor authentication for the adapter user created to collect SaaS Management data.
- Gateway Name - Select the Gateway through which to connect to perform the action.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?