Most MDM problems do not announce themselves. They accumulate quietly. A device that never received an update after a configuration change. A kiosk that has been running an outdated app version for months without anyone noticing. An enrolled device that went offline six weeks ago and was assumed to be decommissioned, but is actually still sitting in a back room. An alert threshold that was set at initial deployment and never reviewed as the fleet grew.
These are not catastrophic failures. They are the kind of gradual drift that makes a device fleet harder to manage over time and more vulnerable when something does go wrong. A periodic MDM audit surfaces all of them before they become operational or security problems.
Here is how to run one and what to look for at each stage.
What an MDM Audit Covers
A thorough MDM audit examines five areas:
- Device inventory and enrollment status
- Configuration profile accuracy and consistency
- App version currency and compliance
- Alert configuration and monitoring coverage
- Access controls and administrative hygiene
Each area can surface specific issues that routine day-to-day management tends to miss. Working through all five gives you a complete picture of your fleet’s actual state versus its intended state.
Step 1: Audit Your Device Inventory
Start with the most fundamental question: do you know exactly which devices are enrolled in your MDM platform and what state each one is in?
In a well-managed fleet, the answer is yes. In practice, most fleets have some inventory drift. Devices were decommissioned without being formally unenrolled. New devices were deployed without going through the standard enrollment process. Devices were transferred between locations and their configuration profiles were not updated to reflect the new assignment.
During the inventory audit, look for:
- Devices enrolled in Moki that are listed as offline for an extended period without explanation
- Devices that appear in the dashboard but are not on the physical asset inventory
- Physical devices that are in use at locations but do not appear in the MDM dashboard, indicating they were never enrolled
- Devices assigned to the wrong location group or configuration profile based on where they are actually deployed
- Devices that have been enrolled multiple times, creating duplicate records that complicate reporting
The output of this step should be a reconciled device list that matches your physical inventory and confirms every device in use is enrolled and assigned to the correct group.
Step 2: Review Configuration Profiles
Configuration profiles are the core of your MDM setup. They define what each device can do, which apps are installed, what the lockdown settings are, and what network and security policies apply. Over time, profiles can drift from their intended state or become outdated relative to the current requirements of the deployment.
During the profile audit, check:
- Whether kiosk mode or device lockdown is enabled on every customer-facing device. Any device that should be locked down but is not represents both a security gap and a brand experience risk. Moki’s kiosk and lockdown features should be active on all devices where they are required.
- Whether devices are assigned to the correct profile for their use case. A POS terminal should be on the POS profile. A digital signage display should be on the signage profile. Misassigned profiles produce inconsistent behavior that is difficult to diagnose without this audit step.
- Whether profile settings still reflect current requirements. A profile created two years ago may have been accurate then but may not account for a new app, a changed network configuration, or an updated security requirement.
- Whether there are redundant or unused profiles in the system that create confusion without serving any current deployment.
Step 3: Check App Version Currency
App version drift is one of the most common and most consequential findings in an MDM audit. When centralized update management is not actively maintained, individual devices end up running different versions of the same app. The symptoms include inconsistent behavior across locations, inability to reproduce issues reported at specific sites, and security vulnerabilities in devices running versions with known bugs.
During the app audit, check:
- Which version of each managed app is currently installed across the fleet
- Whether all devices in a group are running the same version or whether there is version fragmentation
- Whether any devices are running apps that have been officially deprecated or replaced
- Whether the most recent version of each app has been pushed to all applicable devices or whether some groups were missed
- Whether any unauthorized apps appear on devices that should be in full lockdown mode
If version fragmentation is widespread, the remediation is to push the current approved version to all affected devices simultaneously through Moki’s app management capabilities. If specific devices failed to update, investigate why: connectivity issues, enrollment problems, or profile misconfiguration are the most common causes.
Step 4: Review Alert Configuration and Monitoring Coverage
Alerts are the early warning system for your device fleet. Without properly configured alerts, the first indication of a device problem is often a customer complaint or a missed transaction. A well-configured alert system means your team knows about device issues in real time and can begin remote troubleshooting before any customer interaction is affected.
During the alert audit, verify:
- That every device group has alerts configured for the conditions that matter most: device offline, app crash, and low battery are the minimum baseline
- That alert thresholds are set appropriately for the operational context. A device that goes offline for two minutes during a reboot is different from a device that has been unreachable for four hours.
- That alerts are routing to the right people. An alert that fires but goes to a distribution list no one monitors is not providing value.
- That the Moki SDK is configured to capture custom in-app events if your applications support it, enabling more granular alerting beyond device-level health metrics
- That someone on the team is reviewing alert history periodically to identify patterns, such as a device that repeatedly triggers low-battery alerts, indicating a hardware issue that needs attention
Step 5: Review Administrative Access and Permissions
The final area of the audit is administrative hygiene: who has access to the MDM platform and what level of access they have. In most organizations, this is the least-reviewed aspect of device management and often reveals access that should have been removed when employees left or changed roles.
During the access audit, check:
- Which user accounts have administrator-level access to the Moki dashboard
- Whether there are any accounts belonging to former employees or contractors that have not been deactivated
- Whether access levels are appropriate to each user’s role. Someone who only needs to view device status should not have the ability to push configuration changes or wipe devices.
- Whether any shared or generic login credentials are in use that cannot be attributed to a specific individual
Removing stale access and right-sizing permissions is a straightforward security improvement that takes minimal time but meaningfully reduces the risk of unauthorized changes to device configuration.
Running the Audit on a Regular Cadence
An MDM audit is most valuable when it happens on a defined schedule rather than only when a problem forces a review. Quarterly audits work well for most organizations. Annual audits are a minimum. The right cadence depends on how frequently your fleet changes: organizations that are actively deploying new devices, opening new locations, or changing their app stack benefit from more frequent reviews.
Moki’s dashboard makes most of the audit steps straightforward by providing real-time visibility into device status, configuration assignment, app versions, and alert history. The platform gives you the data. The audit gives you the structured process for reviewing it and acting on what you find.