
An MDM solution: which devices and which settings first
An MDM solution rarely fails on the technology and often on the order. Lock everything down on day one and on day two the service desk is full and the board is asking whether it can be switched off. This article covers which devices to enrol first, the five settings that belong there straight away and what to deliberately leave for later.
Start with the devices that open business email and files, not with every device at once. A personal phone often does not need full enrolment at all.
Five settings belong on day one: screen lock, encryption, a minimum operating system version, updates and remote wipe. The rest can wait until that works.
Only tie access to a managed device once you know how many devices are not managed. Measure first, then enforce.
What an MDM solution does, and what it does not
Mobile device management is software that lets you configure, secure and, if needed, wipe business devices remotely. Despite the name it has long stopped being only about phones: the same MDM solution usually manages laptops, tablets and shared devices such as a warehouse scanner or a reception tablet too.
In practice it does three things: let a device set itself up the first time it is switched on, enforce a policy (passcode, encryption, updates) and report which device complies. That is also the limit of the tool: MDM knows what has been enrolled, and nothing about the device that never was.
That is why a rollout starts with a list and not with a policy. How we set up the management itself, and where our line sits at the contract, is on our page about mobile device management; this article is about the order.
First the list: which devices to enrol first
Not every device is equally urgent. A sensible order follows the risk, and the risk sits wherever business data lives:
- Company phones and laptops with business email. They hold the most, they leave the building and you own them, so you may manage them fully. Start here.
- Shared devices. A tablet at reception or a scanner in the warehouse has no fixed user and often runs in a locked mode with one app. Set them up as a group, not per person.
- Personal phones with work email. These are usually not fully enrolled. App protection (often called MAM) protects only the business apps and data without touching the rest of the device.
- Devices that no longer receive updates. You enrol these not to manage them but to find them. They belong on a replacement list, not in a policy.
Count how many of each type there are beforehand. Without that number you will not know later whether a hundred enrolled devices is a success or half of the estate.
The five settings that belong on day one
A first policy is short. The aim is that a lost device does not become a data breach, not that the device is perfectly configured.
- Screen lock with a passcode or biometrics, and a short timeout before the screen locks.
- Storage encryption. On modern phones it is on as soon as there is a passcode; on laptops you check it, because it is not always on by default.
- A minimum operating system version. A device below it is reported, not blocked straight away.
- Updates within an agreed period, so that security updates do not sit for months.
- Remote lock and wipe, with an agreement on who may press that button and who is reachable outside office hours.
On a personal device that last one means: wipe only the work part. Put that difference in the policy so nobody has to decide it case by case.
What you deliberately do later
It is tempting to switch on everything the product can do at once. Each of the following is worthwhile, and each will produce complaints if it arrives in week one:
- Blocking or pushing apps. First see what is actually used, or you will block the app the field engineers plan their day in.
- Restricting the camera, USB storage or Bluetooth. Only where there is a reason, per group, not for everyone.
- Wi-Fi and VPN profiles with certificates. Useful, but one certificate mistake leaves a whole department without a network.
- Access only from a managed device. That is the final step, not the first: see below.
Plan these as a second and third round, with a date. Later is not the same as never.
Enrolment: new is easy, existing is not
A new device that is linked to your organisation at purchase, through Apple Business Manager, Android Enterprise or Windows Autopilot, enrols itself the first time it is switched on and pulls down its configuration. The box can go straight to the employee. That is the easy half.
The hard half is the devices you already have. An iPhone that needs to be fully managed often has to be wiped first; a laptop that has been in use for years has local admin rights and its own software that you will not straighten out in an afternoon. Expect three routes:
- Replace at the next purchase, for devices that are due anyway.
- Rebuild by appointment, with a backup beforehand, for devices that will last for years.
- App protection only, for whatever you cannot or will not wipe.
Ask every device supplier whether they can link devices to your organisation on delivery. If they cannot, every device is manual work.
Rolling out without flooding the service desk
The order that works is much the same everywhere:
- A pilot group of a few people, including at least one field worker and one person who does everything on their phone.
- Measure first, then enforce. Let the policy only report non-compliant devices for a few weeks. Tie access to a managed device straight away and you lock the managing director out on Monday morning.
- Explain privacy up front. Say what the organisation does see (device type, version, whether it complies) and what it does not (personal photos, messages, browsing history). The question will come anyway, and better from you than from the corridor.
- Only then tie access to it. Business email and files only from a device that meets the policy.
In the UK the ICO’s guidance on monitoring workers expects you to tell staff what is collected and why. Involve employee representatives where you have them before you roll out, not after.
Choosing an MDM solution: three questions
There are many MDM solutions and most of them handle the basics. The difference is in how they fit what is already there:
- Which accounts do you already use? If you work in Microsoft 365, Intune is included in some of the licences and links straight to sign-in. A second platform alongside it mainly costs explanation.
- How mixed is the estate? Lots of Apple, lots of Android, rugged scanners, Windows laptops: ask per type how far management really goes, not whether it is “supported”.
- Who manages it afterwards? A product nobody maintains will report neatly in a year that everything complies with a policy nobody remembers.
If something is already running, only replace it once you know why. Two management platforms on the same device is a source of faults nobody can explain.
Where our work stops
What we do. We supply the devices, link them to your organisation at purchase, set up the management platform, write the policy in rounds, run the pilot and the rollout, and then manage the devices through to wiping and disposal. We install the eSIM profile you receive from your network provider onto the device.
What we do not do. We do not supply mobile contracts, SIM cards or call minutes. Your contract, your numbers and your tariffs stay with your provider, and we stay out of that. Nor are we lawyers: whether your privacy notice and your arrangements with staff are legally sound is for someone in that profession to review.
Questions we get about this
The five that come up most often.
What is an MDM solution?
An MDM solution is software that lets you configure, secure and, if needed, wipe business devices remotely. It enforces a policy such as a passcode, encryption and updates, and reports which device complies. Despite the name it usually manages laptops and tablets as well as phones.
Which MDM settings should come first?
Start with five: screen lock, encryption, a minimum operating system version, updates within an agreed period and remote wipe. Blocking apps, Wi-Fi and VPN profiles and access only from managed devices come in a second and third round.
Do personal phones need to be fully enrolled?
Usually not. App protection secures only the business apps and data on the device, and lets you wipe only that part when someone leaves. Full enrolment is meant for company-owned devices.
Can my employer read my messages through MDM?
No, that is not what MDM is for. The organisation sees information about the device, such as its type, its version and whether it complies, but not photos, messages or browsing history. What exactly is visible should be explained to staff beforehand.
Do you also supply mobile contracts and SIM cards?
No. We do not supply mobile contracts, SIM cards or call minutes; those stay with your provider, along with your numbers and tariffs. We supply and manage the devices attached to them, from enrolment to wiping and disposal.
Further reading
What this management connects to.
Shall we decide the first round together?
Tell us how many devices there are, whether they are company-owned or personal and what management is on them now. You will get back which devices come first and which policy goes with them.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.