School Device Management in the UAE: Running iPads, Macs and Chromebooks Through the School Year

School-owned or personal: set the boundary first

Every later decision, from which apps can be installed silently to whether a lost device can be erased, follows from who owns the device and how it was enrolled. Write the boundary down before choosing settings, and share it with staff and parents.

Apple supervises iPads enrolled through Automated Device Enrollment on iPadOS 13.1 or later, and Macs on macOS 10.14.4 or later. Supervising an iPad by hand erases it.

Personal-device enrolment has its own set-up, including a domain the school controls for account-driven enrolment; our guide to enrolling staff-owned phones walks through it. What Abu Dhabi’s regulator expects of school-issued and personal devices is covered in our guide to the ADEK School Digital Policy.

iPads and Macs: Apple School Manager and Automated Device Enrollment

Apple School Manager connects a school’s Automated Device Enrollment, Apps and Books purchases, student information system and Managed Apple Accounts. Linked to FileWave, it lets new iPads and Macs enrol during setup, so nobody has to configure each device by hand.

• Where the devices come from. Automated Device Enrollment works for devices added to the school’s account at purchase, from Apple, an Apple Authorised Reseller or an authorised carrier, or added later with Apple Configurator. Devices bought elsewhere, or second-hand, need to be added before they can enrol this way.
• Assign them to FileWave. Each device is assigned to the school’s FileWave server in Apple School Manager; until then it will not find FileWave during setup.
• Set a minimum version if you need one. FileWave can require a minimum operating-system version at enrolment, which Apple supports on iPadOS 17, macOS 14 and later.
• Macs get the FileWave Client too. A Mac enrolled this way can receive the FileWave Client automatically, which adds Filesets, inventory and the self-service Kiosk to what Apple’s MDM provides.

If the school already uses another device-management service, eligible iPads and Macs on iPadOS 26 or macOS 26 or later can move to FileWave without being erased, but Shared iPads are excluded and apps and settings are rebuilt in FileWave first. Our MDM migration guide sets out the conditions.

Shared iPad, carts and one-to-one iPads

Schools usually run iPads in one of three ways: one iPad per student, carts of iPads shared between classes, or Shared iPad, where several students sign in to the same device with their own Managed Apple Accounts.

What Shared iPad needs

• Hardware. Apple requires at least 32 GB of storage, and the iPad must be supervised.
• Accounts. Shared iPad needs a device-management service and Managed Apple Accounts that the school issues and owns.
• Set-up in FileWave. Shared iPad is enabled in FileWave’s Automated Device Enrollment profile before the iPad activates, where the maximum number of users per iPad is also set.
• Apps. On a Shared iPad, apps can install only when no user is signed in, so schedule app changes outside lessons.

Carts need their own planning. FileWave’s Classroom tools map one cart to a whole class, so a cart that moves between classes needs a clear rule for which class it belongs to at a given time. Charging and storage are a separate question; many schools pair device management with charging trolleys such as LapCabby.

Getting apps and books onto devices

• Assign apps to devices, not students, where you can. Apple lets an app bought through Apps and Books be assigned to a device, which the device-management service then installs with no Apple Account on the iPad.
• Supervised devices install silently. On supervised devices apps install without prompting; on unsupervised devices the user is asked to accept each installation.
• Books go to users. Books from Apple Books must be assigned to users, not devices, so they follow the student’s Managed Apple Account.
• Software on Macs and Windows PCs goes out as FileWave Filesets, piloted on a few lab computers first; our software deployment guide covers testing and staged rollouts.
• Self-service on computers. On Macs and Windows PCs the FileWave Kiosk lets staff install approved software without local administrator rights.

Lab and staff computers: Macs and Windows PCs

Computer labs and staff rooms are where file-level control matters most. FileWave’s Self Healing setting checks the files a Fileset delivered, by default every 24 hours after the client starts and whenever an administrator asks, and puts back any that are missing or changed. Download if Missing replaces only deleted files, and Ignore At Verify leaves a file alone after it is delivered, for files students or staff are meant to change. It restores what FileWave delivered; it does not repair every application fault or recover user work.

Windows PCs can be managed with the FileWave Client alone, or enrolled in Windows MDM through Microsoft Entra ID, which needs Entra ID P1 or P2 or an education or Microsoft 365 bundle that includes it; Microsoft Intune is not required. Campuses with slow links can use FileWave Boosters to cache software for Macs and Windows PCs close to them. A mixed fleet of staff laptops is covered in more depth in our guide to managing Mac and Windows devices together.

Chromebooks stay in Google Admin

Google Admin owns Chromebook enrolment and policy, and enrolling school Chromebooks needs a Chrome Education Upgrade licence. FileWave syncs the full Chromebook list from Google Admin and adds inventory, reporting, custom fields and location tools, so Chromebooks appear alongside the school’s iPads and computers. It does not replace Google Admin, and Google enrolment licensing is separate from FileWave’s.

By default, a wiped Chromebook re-enrols into the school’s Google account automatically, which is what makes a lost or reset Chromebook recoverable. Zero-touch enrolment for new Chromebooks is a Google programme run through a pre-provisioning partner, not something FileWave does.

Classroom tools, filtering and safeguarding: what device management is not

• Not a classroom teaching tool. FileWave describes itself as no traditional classroom management tool. It can deploy Apple’s Classroom app to teachers’ devices and deliver the education configuration for classes created through device management, with rosters imported from a supported student information system. Apple requires the students’ devices in those classes to be supervised.
• Not a web filter. FileWave can push Apple’s basic web content filter to supervised iPads and Macs, but a school that needs category filtering and reporting needs a dedicated filtering service.
• Not antivirus or EDR. FileWave has no built-in antivirus or endpoint detection; it can deploy the school’s chosen security software to Macs and Windows PCs.
• Not compliance on its own. Device settings and reports can be evidence for a regulator’s requirements, but policies, agreements and records make a school compliant. Our ADEK guide separates the IT clauses from the rest.

Preparing devices for a new term

1. Reconcile the inventory. Check which devices last reported recently and which have gone quiet; older inventory stays visible while a device is offline. Our inventory guide explains how to read it.
2. Set update policy. Decide the operating-system versions for the term. FileWave manages Apple updates through declarative device management, which needs iPadOS 17 or macOS 14 or later.
3. Refresh app and book assignments. Release licences from leavers and assign them to new devices and students.
4. Reset what needs resetting. Erase and re-enrol devices changing hands, and confirm Shared iPad user limits for the new timetable.
5. Check Classroom rosters against the student information system before the first lesson.
6. Pilot with one class. Run the new set-up on one class’s devices for a few days, fix what breaks, then roll out year group by year group.

Running a pilot and training administrators

A pilot answers the questions a demonstration cannot: whether enrolment works on the school’s network, whether apps arrive before lessons start, and how teachers and students cope with the first day. Agree what success looks like before starting, for example every pilot iPad enrolled and ready on the first morning, the class’s apps installed, Classroom showing the right roster and a lost-device drill completed.

PRO TECHnology sets up FileWave in FileWave’s cloud or on the school’s own server, links Apple School Manager and Google Admin, builds the first profiles and app assignments with the school’s IT team, runs the pilot and trains the school’s FileWave administrators, with support from Dubai afterwards and FileWave behind us when an issue needs the manufacturer. Self-hosting still depends on Apple, Google and FileWave services, as our on-premises guide explains. Licences are quoted by device count, hosting and term on the FileWave page.

Sources

Checked on 9 October 2026 against FileWave’s knowledge base (version 16.4.1), Apple’s Platform Deployment and education guides and Google’s ChromeOS help. FileWave behaviour can change between versions; check the version you will run.

• Apple: Shared iPad overview
• Apple: About device supervision
• Apple: Content distribution methods
• Apple: Requirements for classes created with an MDM solution
• FileWave: Configure Shared iPad with FileWave
• FileWave: Use Apple Classroom with FileWave
• FileWave: Automated Device Enrollment overview
• FileWave: Chromebook management
• FileWave: Fileset verification (Self Healing)
• FileWave: K-12 schools
• Google: Enroll ChromeOS devices

Frequently asked questions