10 Questions to Ask Before Choosing a Rental MDM System | MDM.Plus

Industry Insights 2026-06-26 Views 47

10 Questions a Qualified Rental MDM System Should Answer

"Can it lock the device?" is the wrong first question. The real test is whether, after a device goes out, the system can keep seeing its state, detect risk, leave evidence and help limit the loss. A qualified rental MDM platform should be able to answer ten practical questions.

Know the device and its state

  • Is it still supervised? The console should show more than a name and serial number: the supervision relationship, the last check-in, and any removal, restore or abnormal offline event. If supervision has lapsed while the dashboard still reads "normal", that is dangerous.
  • What state is it in? Devices can be online, offline, overdue, awaiting return, locked, policy-anomalous or unknown. The system should distinguish long offline periods, policies that never took effect, commands not executed, abnormal state reports, and mismatches between console and device.
  • Is activation lock status clear? MDM status only says whether a device is managed. Activation lock status affects the protection boundary after an incident. Look for a recorded status, changes over time, alerts and traceability.

Know whether actions actually happen

  • Did the policy take effect? "Pushed" is not "applied". Separate created, pushed, received, executed successfully, failed and no-response states.
  • What happens offline? Offline devices are normal; silence is not. Ask when an offline alert fires, whether commands are re-sent on reconnect, whether the device enters priority follow-up, whether risk records are retained, and whether normal and abnormal offline states are distinguished.
  • Is there an overdue loop? Overdue is a workflow, not a button: reminder, state check, policy change, lock or restriction, manual follow-up, logs, then unlock or return handling.
  • Are operations auditable? Record who acted, when, what was done, the device state at the time, success or failure, the failure reason and the linked order or customer. Without records there is no evidence.

Know the limits and the supplier

  • Are data and permissions separated? Merchant data isolation, role-based access, control over provider staff, logs for sensitive actions, backups and masking of customer information.
  • Does an incident reduce resale value? Abnormal devices should become hard to buy, hard to sell, hard to explain and hard to circulate, so recyclers will not pay the normal price.
  • Can the provider respond? Incidents are urgent: a customer at the store, a batch of abnormal states, a certificate failure, a failed command. Look for fixed after-sales, technical support, triage, certificate and server maintenance, major-issue response and post-incident review.

MDM is a long-term service, not a one-off tool. Compatibility applies only to confirmed models, OS versions, permissions and deployment conditions and does not imply official authorisation or endorsement. The final scope is subject to the confirmed product specification and service agreement.

Email 400 816 5855