In these link articles, we will provide detailed steps on how to enrol on your district and how the devices will be linked to the respective schools.
By enrolling in Enterprise Mobility Management (EMM) at the district level, you centralise the administration of your fleet, allowing for more efficient resource allocation. Instead of managing each school with separate EMM configurations, a district-wide setup creates a "central hub" for all your Android devices.
This high-level view ensures that device distribution reduces the technical burden on individual schools while ensuring every student has immediate access to a secure and uniform digital learning environment.
Setting Up Your Android EMM Structure
To get your organisation up and running with Android EMM, we’ll follow a specific organisational structure. This setup ensures your district-level settings stay centralised while keeping individual school folders organised.
Organisational Unit (OU) Requirements
To manage this effectively, you will need to create two distinct types of OUs:
-
The District "Binding" OU: This is your primary hub. You will create one specific Organisational Unit where your EMM configuration is officially bound. This OU can contain "generic users" (for example, Student 1 through Student 20), depending on your total device volume. (avg 10% of the device volume)
- Each user can have multiple device enrolments.
-
The School OUs: You will create separate OUs for each of your school's structure (grades). Critically, these school-level units will not be bound to the EMM configuration, nor will they inherit the settings from the District OU. This keeps your school folders clean and dedicated solely to user organisation.
- Each Student will have their dedicated user account added to these OUs