UEM Foundations · Course F1Lesson 1 of 5
What UEM does
8 min read- Explain the problem device fleets create for organizations
- Trace the MDM → EMM → UEM evolution in one breath
- Name the five jobs a UEM platform performs
Every organization above a certain size wakes up one day owning a fleet: phones in the field, tablets on forklifts, laptops at desks, kiosks in lobbies. Unmanaged, that fleet is three problems at once — a security problem (every device is a door into company data), an operations problem (setup, updates, and repairs by hand), and a compliance problem (no way to prove where data lives or who can reach it).
Unified endpoint management exists to turn that fleet back into a system.
From MDM to UEM
The category grew in three steps, and people still use all three names:
- MDM — mobile device management. The original scope: enroll phones, push settings, lock or wipe them remotely.
- EMM — enterprise mobility management. MDM plus the software layer: managed app catalogs, corporate email and content, separation of work and personal data.
- UEM — unified endpoint management. The convergence: one console, one policy engine, every endpoint class — mobile, desktop, rugged, kiosk, TV.
When someone says "we need an MDM," they almost always mean a UEM. The vocabulary lags the products.
The five jobs
Whatever the vendor, a UEM platform earns its keep doing five things:
| Job | The question it answers |
|---|---|
| Enrollment | How do devices come under management — at scale, without hand-touching each one? |
| Policy | What is each device allowed and required to do? |
| App management | Which software is installed, updated, and configured — and which is banned? |
| Visibility | What's the live state of every device — location, health, compliance? |
| Remote action | When something goes wrong, what can I do from here — lock, wipe, restart, support? |
Everything else a platform offers — kiosk modes, geofences, patch rings, remote screens — is one of these five jobs wearing work clothes.
Why this matters to you
If you sell: every customer pain maps to one of the five jobs, and discovery is just finding which one hurts most. If you deploy: every console screen you'll ever touch implements one of the five. The rest of this course builds the vocabulary those conversations run on.