trio.so
Templates

MDM Implementation Checklist (Free Word + Excel Tracker)

Free MDM rollout checklist in Word and PDF: requirements, APNs and platform prerequisites, a policy baseline, pilot and go-live forms, plus a tracker.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

An MDM rollout tends to go wrong in the same places: an Apple certificate created with someone's personal account, a firewall that quietly breaks enrollment, a pilot with no exit criteria, and staff who first hear about device management from a prompt on their phone. A checklist with an owner and a date on every item catches most of these early.

This one is for IT managers and sysadmins at companies of 20 to 1,000 people rolling out MDM for the first time or switching products, and for MSPs doing it for a client. The download has the checklist in Word and PDF, with a selection checklist, a platform prerequisites sheet, a device control baseline, pilot and go-live sign-off forms, a user notice template and a filled-in example. An Excel tracker covers tasks, certificate and token renewals, enrollment waves, the pilot result and risks.

In short

  • Count devices per platform and ownership type, and write success measures with numbers.
  • Do the platform prerequisites in week one: APNs certificate, Apple Business Manager token, Android Enterprise binding, Windows enrollment method, firewall rules.
  • Test a short policy baseline on one device per platform, then run a pilot with exit criteria agreed in advance.
  • Enroll team by team against a target, and hand over with runbooks and every renewal date in a shared calendar.

How This Checklist Relates to the Implementation Guide

Our guide to mobile device management implementation explains each phase and ends with a 30/60/90-day plan. This page and its download are the working copy: the items to tick, who owns each one and when it is due. Read the guide for the reasoning behind a phase, and run the project from the checklist and the tracker.

The six stages of the checklist, from scope to go-live; the pilot is the gate before any enrollment wave
The six stages of the checklist, from scope to go-live; the pilot is the gate before any enrollment wave

MDM Requirements: A Selection Checklist

Choosing the product comes before the rollout. Section 4 of the download is a one-page selection checklist with columns for two products side by side. The must-haves:

  • Manages every platform you counted, in one console.
  • Zero-touch enrollment: Apple Business Manager or Apple School Manager, Android Enterprise, Windows Entra join.
  • Company-owned and personal devices, with clear limits on what IT can do on personal ones.
  • Passcode, encryption, screen lock and OS update policies, with the status of each policy on each device.
  • App deployment on every platform, including Apple Apps and Books and managed Google Play.
  • OS and third-party app updates, with the result per device.
  • Remote lock and remote wipe of company devices.
  • Directory sync (Entra ID, Google Workspace, Okta or OneLogin) and SCIM provisioning.
  • Console roles and MFA for admins.
  • Device inventory with owner, serial number, installed apps and encryption status, exportable.

Nice to have, depending on your fleet: kiosk mode, USB storage control, Wi-Fi and certificate profiles, remote desktop, single sign-on for users' apps, evidence exports for audits and, for MSPs, several client organizations in one console. Check prices against your device count with our guide to MDM pricing.

Scope and Success Measures

Start with numbers: devices per platform (Windows, macOS, Linux, iOS/iPadOS and Android), who owns each group of devices, and the user groups that need different setups, such as office staff, field staff and shared tablets. Count from purchase records and the user directory rather than from memory; the gap between the two usually turns up devices nobody listed. Then write three to five success measures you can check on go-live day, for example 95% of devices enrolled and every laptop encrypted, and name an owner for each platform. If personal devices are in scope, settle the rules in a BYOD policy before anyone enrolls one.

Platform Prerequisites: Apple, Android, Windows and Linux

Several of these steps wait on another company or another team, so start them in week one.

PlatformWhat you needWatch for
Apple: APNs certificateAn Apple Push Notification service certificate from the Apple Push Certificates Portal, created with a company Apple Account that more than one person can reach.Valid for 365 days. Renew it with the same Apple Account: a new certificate under a different account means enrolling every Apple device again.
Apple Business Manager or Apple School ManagerYour MDM added as an MDM server, its server token loaded into the MDM, devices assigned for automated device enrollment, and Apps and Books if you buy apps.The server token and the Apps and Books token each expire after a year. Put both dates in the tracker.
AndroidAndroid Enterprise bound to the MDM with a company Google account, enrollment tokens or QR codes per group, and zero-touch enrollment through your reseller for new company devices.Decide per group: fully managed for company devices, a work profile for personal ones.
WindowsMicrosoft Entra join with automatic MDM enrollment, or bulk enrollment with a provisioning package for shared and pre-staged PCs.Check the MDM user scope in Entra ID before the pilot.
LinuxThe distributions in scope, the agent's install script and token, and the people who hold root on those machines.Plan how the script reaches each machine.

For the firewall, Apple's enterprise network guide asks you to allow *.push.apple.com on TCP 443, 2197 and 5223, plus its enrollment and MDM hosts, or 17.0.0.0/8 if your firewall only takes IP ranges. Google's Android Enterprise list needs TCP 443 and TCP and UDP 5228 to 5230 to hosts such as play.google.com and fcm.googleapis.com. Both say intercepted HTTPS connections fail, so keep these hosts out of SSL inspection. Finish by enrolling one test device per platform from the office, from home and over mobile data. For the Apple side in more detail, see Apple Business Manager; for new devices that set themselves up, see zero-touch deployment.

Identity, Roles and Groups

Connect your directory (Microsoft Entra ID, Google Workspace, Okta or OneLogin) so users and groups sync into the MDM instead of being typed in, and decide whether accounts arrive by directory sync or SCIM provisioning. Map directory groups to device groups and policies, such as Finance laptops or Warehouse handhelds. In the console, give each admin a role with only the rights their job needs, turn on MFA for every admin account, and write down who may approve a remote wipe. Keep one break-glass admin account with its credentials stored offline for the day the identity provider is down.

A Device Control Baseline

Keep the first baseline short, apply it to one test device per platform, and add a restriction only when you can say why it is there. The download's baseline page has a column to tick for each test device:

ControlStarting pointNotes
PasscodeAt least [6] digits on phones, [12] characters on computers; lock out after [10] failed attempts on phones and [20] on laptopsEvery platform; the CIS 4.10 limits
Screen lock[15] minutes idle or less on computers, [2] minutes or less on phones and tabletsCIS Safeguard 4.3 limits
Disk encryptionOn for the whole diskBitLocker (Windows), FileVault (Mac), LUKS (Linux), passcode-based (iPhone, iPad), storage encryption policy (Android)
OS updatesSecurity updates within [14] days of release; oldest accepted version [n]Defer feature updates on Windows if your apps need testing
USB storageBlocked on [groups that handle customer data]Check per platform: not every MDM can block drives on every OS
Wi-FiOffice networks pushed as profiles, WPA2 or WPA3No shared passwords typed by staff
Certificates[Wi-Fi, VPN, internal app] certificates pushed by the MDMNote the renewal owner
AppsAllow list or block list for [roles]Only where the role needs it
KioskOne app or a fixed set of apps on [shared devices]Reception tablets, scanners, shared PCs

The screen lock and lockout values come from the CIS Controls v8. Safeguard 4.3 caps idle time at 15 minutes on computers and 2 minutes on mobile devices, and Safeguard 4.10 allows no more than 20 failed attempts on laptops and 10 on phones and tablets. Write the rules into an MDM policy; Wi-Fi and encryption have their own templates, the Wi-Fi policy and the data encryption policy.

Apps and Licenses

List the required apps per group and platform, then pick a deployment method for each: an app catalog or package upload on computers, Apple Apps and Books on iPhone, iPad and Mac, and managed Google Play on Android. Buy or move licenses before the pilot. Apple licenses go through Apps and Books in Apple Business Manager, and a token still tied to an old MDM blocks the move. Decide which apps are required and which users install from the catalog, and test the first sign-in of every required app on the test devices.

Pilot Group and Exit Criteria

Pick about 5 to 10% of users, with at least two devices on every platform and ownership type you plan to roll out. Include a manager and someone who calls the helpdesk often. Agree the exit criteria before the pilot starts; the tracker's defaults are:

  • 95% or more of pilot devices enrolled without help.
  • No more than 2 pilot devices with a failed policy.
  • No more than 5 helpdesk tickets from pilot users.

Run it for at least two weeks, long enough to see an OS update and a password change. The pilot sign-off form records the results and the decision: go to wave 1, extend the pilot, or stop and rethink.

Tell Users What Changes

Send a notice at least a week before each wave: what changes, the date, what to do and who to ask. Say what IT can and can't see. On personal iPhones, iPads and Macs enrolled through Apple's personal enrollment, IT can't erase, lock or locate the device; on Android, work apps sit in their own work profile. The download has a notice template you can edit, and the implementation guide covers this conversation in its section on what MDM can and cannot track. If you have a works council or employee representatives, involve them before the pilot, and have HR or counsel review the notice.

Enrollment Waves

Roll out by team or site, so each team changes over on one day and gets help on that day. Each wave gets a date, an owner, a planned device count per platform and a fallback for failed enrollments: a walk-up desk, a spare device or a booked call. The tracker works out each wave's enrollment % and marks it Behind target once its date has passed below the target, 95% by default. Don't start the next wave while the last one is behind.

After the last wave, check that every company device on the asset list is enrolled or has a recorded reason. CIS Safeguards 1.1 and 1.2 cover the asset inventory and devices that shouldn't be on the network. New starters after go-live follow the IT onboarding checklist.

Moving From Another MDM

MDM products rarely import each other's settings, so rebuild policies and apps as a fresh baseline and export the old device list with serial numbers first. Move one group at a time: remove it from the old MDM and enroll it in the new one on the same day. Company iPhones, iPads and Android devices usually need a reset, so plan backups and the time per device, and assign Apple devices to the new MDM server in Apple Business Manager before you reset them. Keep the old licenses until the last wave is done. Moving to trio.so? See switching to trio.so.

Go-Live and Handover

At go-live, the team that runs devices day to day takes over. Hand them runbooks for a lost or stolen device, a new starter, a leaver (the IT offboarding checklist covers the account side), a device replacement and a failed enrollment, plus the admin accounts and the patch schedule. Put the APNs certificate, the Apple Business Manager token and the Apps and Books token in a shared calendar a month before each expiry. Review enrollment, policy failures and tickets after 30 days, and schedule the first audit three to six months out with the MDM audit checklist.

Example: Bramblecote Supply

The download includes a filled-in tracker for Bramblecote Supply, a made-up 260-person distributor rolling out to 339 devices on all five platforms. On 16 November, 12 of its 20 tracked tasks were done and 68% of devices were enrolled:

WavePlatformEnrolled%Check
PilotWindows (company-owned)8 of 8100%On target
PilotmacOS (company-owned)4 of 4100%On target
PilotiOS/iPadOS (company-owned)6 of 6100%On target
PilotAndroid (company-owned)3 of 475%Behind target
Wave 1macOS (company-owned)31 of 31100%On target
Wave 1iOS/iPadOS (company-owned)68 of 7097%On target
Wave 1iOS/iPadOS (personal)10 of 1471%Behind target
Wave 2Windows (company-owned)97 of 12081%Behind target
Wave 2Linux (company-owned)4 of 4100%On target
Wave 3Android (company-owned)0 of 560%In progress
Wave 3Windows (company-owned)0 of 220%In progress

Wave 2's office laptops are three days past their date at 81%, because 23 of them need a firmware update first. The Apps and Books token expired on 10 November, and the Apple Business Manager token runs out two days before go-live. The pilot missed its enrollment target (91% against 95%) and was signed off with one fix. Every admin can still wipe devices, because the console roles are a week late.

Common MDM Rollout Mistakes

  • The APNs certificate was created with someone's personal Apple Account. When they leave, nobody can renew it, and every Apple device has to enroll again.
  • Policies were never tested on one device per platform, so the pilot finds problems that a test device would have shown in an hour.
  • The pilot had no exit criteria, so nobody could say when it was done.
  • Waves were planned by platform. Each team then changed over several times and called the helpdesk each time.
  • Staff heard about the MDM from the enrollment prompt, with no notice and no word on what IT can see.
  • Tokens and certificates expired after the project team moved on, because the dates lived in one person's head.
  • HTTPS inspection on the firewall broke Apple and Google connections, and it looked like an MDM fault.

CIS Controls and NIST SP 800-124

The download's mapping (Appendix F) points each section to these references, as a reading aid:

FrameworkWhere it shows up
CIS Controls v81.1 and 1.2 asset inventory and unauthorized assets; 4.1 secure configuration process; 4.3 automatic session locking; 4.10 device lockout after failed attempts; 4.11 remote wipe on portable devices; 4.12 separate enterprise workspaces on mobile devices.
NIST SP 800-124 Rev. 2Guidelines for Managing the Security of Mobile Devices in the Enterprise (May 2023): recommendations for deployment, use and disposal across the device lifecycle.

Your auditor decides what counts for your scope. Once the MDM is live, the MDM audit checklist tests whether the controls work.

MDM Rollout Tracker (Excel)

The workbook has one tab for each part of the checklist:

  • Tasks holds every checklist item by phase, with owner, due date and status, and flags Overdue, Due soon, No due date and Blocked.
  • Prerequisites lists the accounts, certificates and tokens per platform and flags Renewal due and Expired for the APNs certificate, the Apple Business Manager token and the Apps and Books token.
  • Waves works out enrollment % per wave and per platform and flags waves behind target. Pilot passes or fails each exit criterion against its target.
  • Risks scores likelihood times impact. Settings, Example, Dashboard and Sources hold the thresholds, the filled-in example, % done per phase with enrollment per platform, and the references. Formulas only, no macros.
The tracker's Example tab: a made-up company's enrollment waves, with the checks it raises
The tracker's Example tab: a made-up company's enrollment waves, with the checks it raises

What's in the Download

The checklist PDF: cover, the policy baseline and the filled-in example
The checklist PDF: cover, the policy baseline and the filled-in example
  • Word checklist (MDM-Implementation-Checklist-trio.so.docx): ten phases with owner, due date and a tick box on every item, the selection checklist, the platform prerequisites sheet, the device control baseline, pilot and go-live sign-off forms, the user notice template, a wave plan, the filled-in example and the framework mapping, with fillable fields.
  • PDF (MDM-Implementation-Checklist-trio.so.pdf): the same checklist, forms and example, ready to print.
  • Excel tracker (MDM-Rollout-Tracker-trio.so.xlsx): the tabs described above.

Where trio.so Fits

trio.so is an MDM you can roll out with this checklist. It covers the device side of every phase, from enrollment and the policy baseline to apps, updates and the runbooks after go-live. Scope, the pilot decision, the user notice and the works council stay with you. In practice that means:

  • Windows, macOS, Linux, iOS/iPadOS and Android in one console.
  • Enrollment through Apple Business (formerly Apple Business Manager) or Apple School Manager, Android Enterprise, and Entra join or bulk enrollment with a provisioning package on Windows; Linux enrolls with an install script and token.
  • Adding several devices at once, with an enrollment link emailed to each person.
  • User and group sync from Microsoft Entra ID, Google Workspace, Okta and OneLogin, and SCIM 2.0 provisioning.
  • Console roles, so each admin gets only the permissions their job needs; MFA and single sign-on for your users are in the Zero Trust plan.
  • BitLocker on Windows, FileVault on Mac, passcode policies for iPhone, iPad and Android, and required storage encryption on Android.
  • Policy status for each device: applied, failed or pending.
  • A block on USB storage for company-owned Windows, Linux and Android devices and supervised iPhones and iPads (Macs have no storage block).
  • Wi-Fi profiles with WPA2 or WPA3 on Windows and Apple devices, and PKCS#12, SCEP and root certificates on Apple devices and Windows.
  • Kiosk mode on Android, iPhone and iPad, Mac and Windows.
  • App deployment from an app catalog and MSI uploads on Windows, DMG uploads and Apple Apps and Books on Mac, Apple Apps and Books on iPhone and iPad, and managed Google Play on Android.
  • OS updates through Auto Patch policies and third-party fixes through remediation plans, with the result shown for each device.
  • A device inventory with each device's owner, serial number, installed apps and encryption status.
  • Remote lock on Mac, iPhone, iPad and Android, and remote wipe of company-owned devices.
  • Remote desktop for support, with a log of each session.
  • On personal iPhones, iPads and Macs, IT can't erase, lock or locate the device; on Android, work apps sit in their own work profile.
  • Compliance evidence exports, and a CSV export of console members with their roles and last-active dates.
  • A multi-client console for MSPs, with its own devices, users and policies for each client.
  • A switch page with the current offer for teams moving from another MDM.

It doesn't pick your scope, decide when the pilot passes or talk to your works council. It also doesn't record what people do on their devices: it shows the state of the device, not the activity of the person using it. It manages Windows, macOS, Linux, iOS/iPadOS and Android from one console. Plans start at $5 per device.

Start free trial Book a demo

14-day free trial. No credit card required.

Related Templates and Guides

Sources. Last reviewed November 2026. Framework references are short pointers to the CIS Controls v8 and NIST SP 800-124 Rev. 2; network and certificate details come from Apple, Google and Microsoft documentation. The wording is ours. trio.so is not affiliated with or endorsed by the Center for Internet Security, NIST, Apple, Google or Microsoft.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Run this checklist on trio.so

trio.so manages Windows, macOS, Linux, iOS/iPadOS and Android in one console, with enrollment through Apple Business, Android Enterprise and Entra join, passcode and encryption policies, and each policy's status per device.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

Scope and success measures, a selection checklist, platform prerequisites (APNs certificate, Apple Business Manager, Android Enterprise, Windows enrollment, firewall rules), identity and admin roles, a policy baseline, apps, a pilot with exit criteria, a user notice, enrollment waves, and a go-live handover with runbooks and renewal dates.

On your side: a device count per platform, an APNs certificate for Apple devices, Apple Business Manager or Apple School Manager for zero-touch Apple enrollment, an Android Enterprise binding, a Windows enrollment method, directory access and firewall rules for Apple's and Google's endpoints. For the product itself, use the selection checklist.

A small company can finish in a few weeks: about a week for prerequisites, one to two weeks of pilot, then the waves. Apple and Android steps that wait on resellers, and a move from another MDM, add time. The tracker shows which dates are slipping.

Sign in to the Apple Push Certificates Portal with the Apple Account that created the certificate, renew it with a new request from your MDM, and upload the result to the MDM. It is valid for 365 days. A new certificate under a different account means enrolling every Apple device again.

About 5 to 10% of users, with at least two devices on each platform and ownership type you plan to roll out, plus a manager and someone who calls the helpdesk often. Agree exit criteria first, such as 95% enrolled without help, at most 2 devices with a failed policy and at most 5 tickets.

Yes, under a BYOD policy. Apple's personal enrollment covers iPhones, iPads and Macs, and IT can't erase, lock or locate those devices. On Android, a work profile holds the work apps. Tell staff before they enroll what IT can and can't see.

Export the device list, rebuild policies and apps in the new product, then move group by group, removing and enrolling on the same day. Company iPhones, iPads and Android devices usually need a reset, and Apple devices have to be assigned to the new MDM server in Apple Business Manager first.

Related

From the blog

The related industry news, interviews, technologies, and resources.