Platform compatibility
| macOS | Windows | Linux | iOS / iPadOS | Android |
|---|---|---|---|---|
| ✅ | ✅ | ✅ | ❌ | ❌ |
Prerequisites
- An existing MDM, Active Directory with GPO, or equivalent system capable of deploying packages to your devices.
On macOS, once the Fleet agent is installed silently, the MDM enrollment profile still needs to be installed by the employee. For a fully touchless experience, use Zero Touch for Apple instead.
Deploy via an existing MDM
Download the enrollment packages from Devices > Enroll devices in the Primo cockpit. Select the operating system and copy the package or download the installer. Distribute the package through your existing MDM (Jamf, Intune, SCCM, etc.) as a silent install. The agent will check in with Primo automatically once installed.Migrate from another MDM
Windows — automatic migration
Enable Windows MDM Automatic Migration in Settings > MDM. Once enabled, Fleet will automatically migrate Windows devices enrolled with another MDM solution — no manual re-enrollment required.Migrating from Intune specifically
If you have connected Intune and Entra ID, follow these steps before initiating migration:Set Fleet as the external MDM in Entra
Go to your Fleet MDM URL:
https://{company}.mdm.getprimo.com/settings/integrations/automatic-enrollment/windowsSwitch automatic enrollment to Fleet in Entra
Go to entra.microsoft.com and search for Mobility. Select Intune, then set both options to None and save.
Migrate devices
- One by one: enroll the device in Primo — it will appear with the status “On in another MDM”. Use the migration button in Primo to run the migration script.
- All at once: upload the migration script to Controls > Scripts, create a policy using the detection query below, and link the script to the policy.
INPUT_URL_HERE with your Fleet MDM URL):macOS — supervised devices (registered in ABM)
Connect Primo to your Apple Business Manager
Go to Settings > MDM > Apple and complete the ABM connection.
Reassign devices in ABM
In Apple Business Manager, reassign devices to Primo’s MDM server. This does not erase device data.
Remove the old MDM profile
From your previous MDM console, unenroll the devices. ABM does not remove them automatically.