Mobile device management (MDM) fundamentals
You learn how an organisation manages its fleet of phones and tablets: enrolment methods, ownership models, policies, app distribution, compliance and lost-device actions, all tried on a simulated management console.
Level 201 · 22 lessons · 18 practice labs
Lessons
Core concepts
- Why devices are managed: data, access and accountability
- MDM, EMM and UEM: the terms and their scope
- Ownership models: BYOD, COPE, company-owned, shared
- How MDM talks to a device: push, command, status report
- Short task: pick the right ownership model for three scenarios and justify it
Enrolment
- Enrolment methods: user enrolment, automated enrolment, QR code
- Zero-touch and automated device enrolment
- Enrolment tokens and device certificates
- Unenrolment and retiring a device
- Short task: find the half-enrolled and ownerless devices in the inventory
Policies and apps
- Passcode and encryption policy
- Restriction policies: camera, backup, unknown sources
- Wi-Fi, VPN and certificate profiles
- App distribution: required, optional and blocked apps
- Operating system update policy
- Short task: find and fix three weak settings in a policy file
Compliance and actions
- Compliance rules: version, passcode, encryption, root access
- Inventory and reporting
- Lost-device actions: lock, locate, full and selective wipe
- Privacy on managed devices: what the admin can and cannot see
- Short task: pull a non-compliant device report from the simulated console and group it by cause
Capstone
- Capstone: write the baseline policy set for a thirty-device office and audit the inventory
Practice labs
- Pick the ownership model for three scenarios: Justify the choice of BYOD, COPE or company-owned for field staff, an executive and an intern.
- Match the enrolment method to the device type: Write the enrolment method and reasoning for Karaçam Mobilya's shop tablets and staff phones.
- Prepare an enrolment plan for a hundred devices: Write the plan covering zero-touch, user enrolment and retirement steps, with owners.
- Pull the device list from the simulated console: Fetch the inventory from the API and state the device count per platform.
- Find the half-enrolled and ownerless devices: Use jq to filter devices with no assigned user and no check-in for thirty days.
- Match leavers' devices against the inventory: Compare the leaver list with the inventory, find devices still enrolled and write the closing steps.
- Read the passcode setting in a policy file: Find the minimum length and auto-lock value.
- Fix three weak settings in a policy file: Fix the short passcode, the encryption requirement turned off and unknown sources left on.
- Write a baseline policy set for a thirty-device office: Write passcode, encryption, update and restriction policies for Sedirli Hukuk Bürosu and have the console validate them.
- Read the security type in a Wi-Fi profile: Find the network name and authentication type in the profile file.
- Arrange the required and blocked app lists: Make one app required and one blocked in the policy file and resolve the conflict.
- Turn shared-password Wi-Fi into a certificate-based profile: Replace a shared-password network profile with one that authenticates by device certificate and validate it.
- List the non-compliant devices: Pull the compliance state from the console API and count the non-compliant.
- Group non-compliance by cause: Produce separate lists for version, passcode and encryption causes.
- Write a one-page compliance summary for management: Produce from the data a summary with rates, the most common cause and three recommendations.
- Pick the right action for a lost device: Write the lock, selective wipe or full wipe decision for a personal and a company device.
- Carry out a lost-device action on the simulated console: Send lock and selective wipe commands and confirm the status response.
- Write a what-the-admin-can-see notice for staff: Examine the fields the console collects and prepare a clear privacy notice for BYOD users.
About this course
You learn how an organisation manages its fleet of phones and tablets: enrolment methods, ownership models, policies, app distribution, compliance and lost-device actions, all tried on a simulated management console.
What you will learn
- Core concepts
- Enrolment
- Policies and apps
- Compliance and actions
- Capstone
Prerequisites
Finishing the level 101 courses of the same path, or knowing those topics, is enough.
Lab environment
Lessons run in your own Kali Linux terminal that opens in the browser. Nothing to install; the lab starts clean in every lesson.
Frequently asked questions
- Is this course right for my level?
- The course is at level 201; it assumes you know the topics of the lower-level courses.
- Is there anything to install?
- No. Every lesson runs in your own lab environment that opens in the browser.
- How do lessons work?
- Each lesson has 8 to 10 steps and a short quiz. Early steps show the command to type, later steps give less help; if two attempts fail, the solution opens.
- Can I try it for free?
- Yes. The first three lessons of every course are free.