Tech Harmony in Schools: The Importance of Universal Device Management
Mobile Device Management (MDM) is a critical component of any IT Department, yet it can be incredibly challenging in a K-12 environment. Device management is both essential to keeping your devices operational in support of teaching & learning while also a critical tool in the defense of your district. However, it is not uncommon to find every single type of device within a school district, which means that IT leaders need to be experts in multiple device operating systems while simultaneously experts in multiple MDM platforms.
Why is MDM so crucial in schools? The challenge lies in the sheer complexity of managing a wide range of devices and operating systems AND protecting our community from external threats. Think of your role as an orchestra conductor; you should have basic knowledge of how each instrument works but you can’t expect to be an expert in all; your role needs to be to ensure they’re all playing the same song. Don’t focus on the solos, though. Instead, keep your attention on the orchestra.
Here's the reality: K-12 schools rarely deal with a single, standardized device. Some districts have a single platform across all students & teachers, however the norm is to have a Noah’s Arc of devices.
Windows laptops: Often utilized by administrative staff for tasks such as finance, HR, and secretarial duties.
Chromebooks: Popular in classrooms for their ease of use and integration with Google Workspace, although rarely used by staff/teachers.
Macs: Increasingly common, particularly in creative disciplines and upper-level education. They are also common with adults and common staff/teacher devices.
Android tablets: They had a rocky start and have very little usage in K-12 outside of computer science programs, however, there are a large number of interactive whiteboards/screens that run on the Android operating system.
iPads: Frequently found in elementary education, with a broad selection of educational apps. They're also very common in special education programs or other specialized programs that require a specific iOS app.
A Variety of Peripherals and Specialized Devices: This includes interactive screens, 3D printers, and the occasional robot that no one quite knows how to program.
Adding to this complexity, many districts also grapple with BYOD (Bring Your Own Device) policies, which introduce a further layer of management and security considerations.
While MDM solutions offer significant benefits, there are important factors to consider when selecting and implementing them:
Cost: They are expensive, often requiring a per-device license that can quickly add up in K-12 environments, where budgets are tighter than a drum. Districts often look for low-cost or free MDMs, but you-get-what-you-pay-for, and free MDMs can sometimes miss important features. I have used MDM platforms that are roughly $1 a device, all the way up to MDMs that are $15-20 per device each year.
Platform Specialization: MDM platforms usually specialize in certain platforms, which means their capabilities in other platforms can be limited or non-existent. It’s rare to find a platform that has expertise across all platforms that doesn’t also break the bank. This can also result in school districts managing multiple MDM platforms to account for the variety of devices, turning IT departments into multi-platform jugglers.
Complexity: They can get complicated really fast, and we can’t expect K-12 IT departments to have detailed expertise across all platforms. Keep in mind, the person managing your devices is probably the same person managing the contracts, bids, repairs, updates, and supporting the use of devices (i.e., standardized test administration). This applies to all the different device platforms and the different MDM platforms a district needs to manage. In the world of K-12 IT, you're not just an expert; you're a Swiss Army knife.
So, should we strive to have ONE MDM platform to rule them all? Or buy best-of-breed for each platform? That’s a decision you’ll ultimately need to make based on what works best in your environment. Each has its pros and cons, and neither is ideal for every situation. However, here are some basic recommendations to ensure you are solving more problems than you're creating:
Prioritize Your Main Targets: Your MDM should be able to manage your main student and staff devices before you start looking at other smaller groups of devices. Don’t get me wrong—we’re all thinking about the damage an AP Comp-sci student can do with an unmanaged Android device, but don’t let this take too much of your attention. Focus on the devices that are most critical to daily operations.
Balance Breadth and Depth: It's generally more effective to have fundamental management capabilities across all your devices rather than advanced capabilities on only a subset. Prioritize MDM solutions that offer broad visibility and control over your entire device fleet, even if it means sacrificing some of the bells and whistles offered by highly specialized systems focused on only one type of device. Going back to the orchestra example; your role as conductor is to make sure the instruments are playing well together, not be an expert in one or more instruments.
Prioritize Core Functions: MDM platforms are used for two main functions in a school district: maintaining your fleet and mitigating security risks. There are a few functions that I think help with both of these areas. We can all add more things that we’d like to have, but these are the four categories that I would first prioritize across all of my devices:
Basic stats on device usage, including the most recent user and login times.
Ability to push updates and remotely shut down/reboot. This helps with basic maintenance and can be critical in a security event.
Ability to push, update, or remove software (including your endpoint protection).
Ability to restrict access to certain functions of the device from unauthorized users. This includes students and external threat actors.
Inventory is Key: Managing an accurate inventory of devices is incredibly painful in a K-12 environment, but your MDM can help, even if it’s just the ability to export the data. You need to be able to show your leadership basic information on device usage, lost assets, or get their help to clean up some bad behaviors.
In essence, MDM provides the centralized control and comprehensive oversight necessary to effectively manage technology in today's K-12 schools. It empowers educators to focus on instruction, empowers students to engage with technology in a productive manner, and equips IT staff with the tools they need to maintain a secure and efficient digital learning environment.
Remember, the goal is to be a skilled conductor, ensuring all instruments (devices) play in harmony, rather than a virtuoso focused on a single instrument.
