The first 30 days of an MDM deployment are the most consequential. The decisions made and the work completed in this window determine whether the fleet is organized and manageable for the long term or whether it accumulates the kind of structural problems that become harder to fix the longer they persist.
Most organizations focus almost entirely on enrollment during this period and treat everything else as something to address later. Configuration profiles get built quickly and incompletely. Alert thresholds are left at defaults or not set at all. Device groups are created ad hoc as devices are enrolled rather than planned in advance. Documentation never gets written because there is always something more urgent.
The result is a fleet that technically functions but does not operate efficiently, and that requires significant remediation work three or six months later when the gaps become operational problems.
This checklist organizes the first 30 days into four distinct phases that build on each other. Completing them in order produces a fleet that is enrolled correctly, configured consistently, monitored proactively, and documented well enough that anyone on the team can manage it.
Days 1 to 7: Foundation
The first week is about building the infrastructure that everything else depends on. No devices should be enrolled until this phase is complete.
- Connect Moki’s MDM platform to Apple Business Manager if the fleet includes iOS devices, confirming that the MDM server token is active and devices purchased through Apple’s channel will enroll automatically
- Set up the Google Zero-Touch portal integration if the fleet includes Android devices, confirming that the correct reseller account is linked and device pre-registration is working
- Define the device group structure before the first device is enrolled, creating location groups for every current deployment site, device type groups for every category of device in the fleet, and platform groups if the fleet includes both iOS and Android
- Build and test configuration profiles for every device type, including kiosk mode or lockdown settings, app lists, Wi-Fi profiles, screen timeout and idle behavior, and security restrictions
- Define the device naming convention and document it so every enrolled device receives a consistent name that identifies its location, type, platform, and unit number
- Create the physical asset inventory template that will be maintained alongside the Moki dashboard record
Do not enroll production devices until every profile has been tested on a single device from unboxing through live customer-facing operation and confirmed to work correctly end to end.
Days 8 to 14: Enrollment
With the foundation in place, the second week focuses on getting devices into the platform correctly.
- Enroll all devices through the appropriate method for each platform, using zero-touch or Apple Business Manager automated enrollment wherever possible and manual enrollment only where automated provisioning is not available
- Confirm that each device receives the correct configuration profile immediately upon enrollment and appears in the correct device groups
- Verify that kiosk mode or lockdown is active on every customer-facing device and that the designated app launches correctly at startup
- Confirm that all required apps are installed at the correct version on every enrolled device
- Verify that Wi-Fi profiles are applied and devices connect to the correct network automatically
- Record the serial number, asset tag, Moki device name, location, and enrollment date for every device in the physical asset inventory
- Flag any devices that did not enroll cleanly or that received incorrect configuration for immediate remediation before they ship to locations
The goal at the end of this phase is a complete, accurately inventoried fleet with every device in a confirmed, tested configuration state.
Days 15 to 21: Monitoring and Alerts
The third week focuses on the monitoring infrastructure that turns the fleet from a collection of deployed devices into a proactively managed operation.
- Configure device offline alerts for every device group, setting thresholds appropriate to the operational importance of each device type. POS terminals and high-traffic kiosks should have tight thresholds of 5 to 10 minutes. Signage displays in lower-traffic areas can tolerate 15 to 30 minutes.
- Configure battery level alerts for any device operating on battery power, setting the threshold high enough to allow time for intervention before the device powers off
- Configure app crash alerts for every managed application on customer-facing devices so the team is notified immediately when an app stops running
- Set up alert routing so notifications reach the correct person or team for each alert type, with an escalation path for alerts that are not resolved within a defined window
- Test every configured alert by triggering the alert condition on a test device and confirming the notification fires correctly and routes to the right recipient
- Configure scheduled reboots for devices that benefit from regular restarts, scheduling them during off-hours to avoid disrupting customer interactions
- Review Moki’s remote control capabilities and confirm that the team knows how to initiate a remote reboot, view a live screen, and push an emergency app update for each platform in the fleet
Do not consider the fleet live until alerts have been tested and confirmed. An alert configuration that looks correct but fails to deliver notifications provides false assurance.
Days 22 to 30: Documentation and Handoff
The final phase captures everything built in the first three phases into documentation that makes the fleet manageable by anyone on the team, not just the person who built it.
- Write or update the device deployment playbook to reflect the enrollment process, configuration profile structure, device group organization, and naming convention actually used during this deployment
- Document the alert configuration including thresholds, routing, and the escalation path for each alert type
- Document the app update process including how updates are tested, approved, and pushed to the fleet
- Document the response procedure for the most common device issues: device offline, app crash, device requiring physical swap
- Document the decommission process including remote wipe requirements and disposal standards
- Conduct a walkthrough with every team member who will be involved in ongoing fleet management so they are familiar with the Moki dashboard, know where the documentation lives, and understand their role in the response and escalation process
- Schedule the first periodic fleet audit for 90 days out to review device inventory accuracy, configuration profile currency, alert configuration effectiveness, and app version compliance
The documentation produced in this phase is what separates a fleet that is managed well indefinitely from one that becomes difficult to manage when the original setup person is unavailable.
What Comes After Day 30
A fleet that completes this checklist in the first 30 days has a solid operational foundation. Every device is enrolled with the correct configuration. The group structure supports efficient targeting for updates and content pushes. Alerts are configured and tested. Documentation is in place.
From this point, fleet management becomes a rhythm of scheduled updates, periodic audits, and alert response rather than constant firefighting. The ongoing management workload is dramatically lower than it would be for a fleet that skipped the foundation work.
Moki’s onboarding team works through many of these steps with new customers during initial setup. Schedule a Moki demo to see how the platform supports a structured onboarding process, or start a free trial to begin building your fleet foundation today. Moki’s eBook library includes additional resources for teams planning their first deployment.