Deploy Aikido Device Protection with Omnissa Workspace ONE
Use Omnissa Workspace ONE UEM to deploy Aikido Device Protection across your managed macOS fleet with the required permissions in place.
All devices must be enrolled in Workspace ONE UEM before you begin.
Installation
What you'll need
Before starting, make sure you have the following from the Aikido Device Protection dashboard:
Your Device Protection Token (copied from the user group selector)
The Shared Root CA Certificate (
.pemfile — downloaded in the dashboard)The Aikido Device Protection installer (
.pkgfile — downloaded in 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.
Add the Aikido Device Protection configuration profile
In the Workspace ONE UEM console, go to Resources → Profiles and Baselines.
Click Add, then Upload Profile.
Select macOS and upload the downloaded
.mobileconfigfile.Click Save and Continue.
Assign the profile to the target smart group.
Click Save & Publish.
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.
Deploy the Aikido Device Protection CA certificate
In the Workspace ONE UEM console, go to Resources → Profiles and Baselines.
Click Add → Add Profile → macOS.
Add a Credentials payload, set the credential source to Upload, and upload the Shared Root CA Certificate (
.pemfile).Assign it to the same smart group and click Save & Publish.
Create the pre-install script
In the Workspace ONE UEM console, go to Resources → Scripts.
Click Add and select macOS.
On the General tab, give the script a name (e.g. "Aikido Device Protection Token").
On the Details tab, set Script Type to Zsh and enter the script below. Replace
AIK_SAFE_CHAIN_TOKENwith your real token.
#!/bin/zsh
# Write the token so the agent registers with the correct user group
echo "AIK_SAFE_CHAIN_TOKEN" > /tmp/aikido_endpoint_token.txt
# Signals the installer to run completely silently, with no user prompts
touch /tmp/aikido_endpoint_mdm_install.txtOn the Assignment tab, assign the script to the same smart group.
Click Save.
Run the script using Run Now and confirm it completes on your test device before you deploy the package.
Scripts require Intelligent Hub 20.10 or later on the device.
Upload the Aikido Device Protection installer
Generate a
.plistmetadata file for the package using the Omnissa Admin Assistant Tool — drag and drop the.pkgonto the tool.In the Workspace ONE UEM console, go to Resources → Apps → Native → Internal.
From the Add dropdown, select Application File.
Upload the Aikido Device Protection
.pkgand click Save, then Continue.Upload the generated
.plistmetadata file and click Save, then Continue.Assign the app to the same smart group and publish.
Deploy in the right order
Deploy the configuration profile and CA certificate before the installer for a smoother rollout.
Save and publish the Aikido Device Protection configuration profile.
Save and publish the Aikido Device Protection CA certificate profile.
Verify both are installed on a test device — Workspace ONE doesn't guarantee delivery order within a smart group.
Run the pre-install script to write the token and confirm it completes.
Publish the Aikido Device Protection app.
Reboot devices after installation
In the Workspace ONE UEM console, go to Devices → List View.
Filter to the target smart group, select all devices, and click More Actions → Restart.
The agent fully activates on the next boot.
Verify the deployment
On a test device, confirm:
The system extension is activated:
systemextensionsctl list | grep aikidoExpect to see the extension marked
[activated enabled].Open System Settings → General → Login Items & Extensions and confirm the Aikido Device Protection entries cannot be toggled off.
Troubleshooting
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?