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 Information Security Officer
Every mainstream platform is covered, including Linux, ChromeOS and tvOS with published minimum OS versions, and zero-touch is documented for Apple through ABM/ASM, Android zero-touch and Knox Mobile Enrollment, and Windows Autopilot with self-deploying and pre-provisioning modes. The Android work profile for BYOD, QR and afw# enrolment, shared-device modes, a rugged-device module and migration paths via Hexnode Gateway and co-management are all described, though the Android Enterprise migration requires re-enrolment rather than an in-place upgrade. 19 27 3 20 9 8 7