For the complete documentation index, see llms.txt. This page is also available as Markdown.

Deploy Device Protection with Jamf

Use Jamf Pro to deploy Aikido Device Protection across your managed macOS fleet with the required permissions in place.

These steps use Jamf Pro. If you use Jamf School, the menus and payload names can differ.

Installation

1

What you'll need

Before starting, make sure you have the following from the Aikido Device Protection dashboard:

  • The Aikido Device Protection .mobileconfig (downloaded from the Aikido Device Protection dashboard)

  • The Aikido Device Protection installer (.pkg file, downloaded from the dashboard)

If you're missing any of these, go back to the Aikido Device Protection dashboard, click Connect Device, and complete the pre-flight steps.

2

Add the Aikido Device Protection configuration profile

  1. In Jamf Pro, use the upload to add it as Configuration Profile for macOS.

  2. Upload the .mobileconfig file.

  3. Scope it to the target devices.

This profile allows the Aikido Device Protection system extension to load silently, enables the network content filter, and stops users from disabling background services in System Settings → Login Items.

3

Upload the Aikido Device Protection installer

  1. In Jamf Pro, go to SettingsPackages.

  2. Upload the Aikido Device Protection .pkg.

  3. Confirm the package finishes processing before you use it in a policy.

4

Create the install policy

  1. In Jamf Pro, go to ComputersPolicies.

  2. Create a new policy scoped to the same devices.

  3. Add the uploaded Aikido Device Protection package to the policy.

5

Deploy in the right order

Deploy the configuration profile before the installer for a smoother rollout.

  1. Deploy the Aikido Device Protection configuration profile.

  2. Verify it has reached all target devices. Check profile status in the Jamf Pro console.

  3. Deploy the Aikido Device Protection install policy.

6

Reboot devices after installation

  1. In Jamf Pro, go to ComputersPolicies and create a new policy.

  2. Add a Restart Options payload and set it to Restart.

  3. Scope it to the same target devices and trigger it after the agent package has installed.

The agent fully activates on the next boot.

7

Verify the deployment

On a test device, confirm:

  1. The system extension is activated:

    systemextensionsctl list | grep aikido

    Expect to see the extension marked [activated enabled].

  2. Open System SettingsGeneralLogin Items & Extensions and confirm the Aikido Device Protection entries cannot be toggled off.

Troubleshooting

Problem
Fix

Users still see the popup

Make sure the configuration profile is scoped correctly and installed before the package policy runs

Extension is waiting for user approval

Check the System Extensions payload and confirm the team ID and bundle ID match exactly

The package installs but the device does not connect

Confirm the token script ran before the package install and that the token was copied correctly

Duplicate extension entries appear

Reboot the device

The content filter is not approved silently

Re-upload the .mobileconfig profile and verify it is installed on the device

Last updated

Was this helpful?