Enrolment & platform coverage
How this is scored
How devices get under management and which ones: the operating systems managed (iOS and iPadOS, macOS, Android, Windows, ChromeOS, Linux, tvOS) and to what depth, zero-touch enrolment through Apple Business Manager (Automated Device Enrollment), Android Enterprise zero-touch and Samsung Knox Mobile Enrollment and Windows Autopilot, QR code and email enrolment, BYOD user enrolment and the Android work profile, supervised and corporate-owned modes, shared devices, rugged and dedicated devices, and migration from another MDM.
0 — Manages no phones, tablets or laptops; a different kind of product.
3 — One or two platforms with manual enrolment; zero-touch enrolment, BYOD and the depth of management per platform are basic or not described.
5 — iOS, Android and Windows or macOS managed, Apple Automated Device Enrollment and Android Enterprise supported, Windows Autopilot or an equivalent described, BYOD enrolment with a work profile or user enrolment, and supervised or fully managed modes for company devices.
8 — Every mainstream platform with feature depth stated per OS, Android zero-touch and Samsung Knox, shared iPad or shared device modes, enrolment of rugged and dedicated devices, a documented migration path from another MDM, and enrolment customised per department or site.
10 — Enrolment a large mixed fleet runs on: every platform above including Linux and ChromeOS with a feature matrix per OS, zero-touch on all of them, migration without wiping documented, and enrolment flows that assign the right profile, apps and owner automatically from the directory.
The Mac Fleet Administrator
The managed-platform list is as wide as I have seen — Android, iOS/iPadOS, macOS, Windows 10 and 11, Linux, ChromeOS, Wear OS, VR and IoT — with Apple Business Manager steps documented for bulk iOS/macOS, Android zero-touch alongside Samsung Knox Mobile Enrollment and QR enrolment, Windows Autopilot, and BYOD work-profile, fully managed and company-owned work-profile modes plus shared-device kiosk. The documented gaps that matter to me: we found no public information on a migration path from another MDM, a per-OS feature matrix, or enrolment flows customised per department or site. 1 2 12 13