Skip to main content
Jamf School, India

Jamf School: iPad management built around a timetable, not an IT department.

Every mainstream MDM was designed on one assumption: whoever is holding the device is an employee. Schools break that assumption completely. The user is nine, the iPad leaves the building every afternoon, a parent has firm views about evening screen time, and a teacher needs thirty screens frozen in the next four seconds without opening a helpdesk ticket. Jamf School was designed around that reality instead. We deploy and operate it for schools throughout India, remotely from Gachibowli, Hyderabad, as a listed Apple Jamf Partner.

Book an education device reviewSee what it covers
Apple device management for schools in India
  • Zero-touchDevices arrive ready to use
  • Teacher-ledClass control without IT
  • Parent appManaged screen time at home
  • Term-readyDeployed in the holiday window
What Jamf School covers

Eight things a school actually needs from device management.

Three separate apps, one each for teachers, students and parents, sitting under an admin console kept deliberately plain because school IT departments are rarely more than two people. We run this for CBSE, ICSE, IB and Cambridge schools, for preschools and for training institutes across the country. Read the list below and notice that each item traces back to a school asking for something a corporate MDM simply could not do. That is the real case for education-specific management, not a marketing tier but a genuinely different set of requirements.

Zero-touch deployment at scale

Buy through an authorised education reseller who registers the hardware to your school and the devices build themselves the first time they are switched on, arriving with apps, restrictions, network settings and class membership already in place. Picture the alternative in the week before term: one technician, several trolleys, four hundred iPads, configuring each by hand. It does not scale, and it quietly undoes itself the first time a student wipes a device in week three.

Jamf Teacher for classroom control

A teacher can see every screen in the room, push the whole class into a single app, lock the devices when attention drifts, and release everything at the bell, with no involvement from IT at any point. Consider what happens without this: a teacher watching half the class slide into a game has to raise a ticket. They will do that exactly once. After that the trolley stays in the cupboard, and a substantial investment becomes furniture.

Jamf Student for a defined space

The student sees a defined space on their own device: which apps are theirs to install, what this particular lesson requires of them, and where they can act without permission. The framing matters more than it sounds, because it communicates an expectation rather than simply blocking things, and any teacher of senior students will tell you that a bare restriction reads as an invitation.

Jamf Parent for home use

For one-to-one programmes where the iPad goes home, parents receive real but bounded authority over evenings and weekends, inside limits the school defines. Get the boundary wrong in either direction and you feel it. Too restrictive and every complaint about homework time lands on your IT lead. Too permissive and a parent can disable protections the school remains legally accountable for.

Jamf Assessment for supervised exams

During an examination a proctor can see what is on each student screen, and that single capability is what separates digital assessment that will survive scrutiny from digital assessment that is merely convenient. Where your board or curriculum body permits on-device exams, this is how a written commitment to exam integrity becomes something you can actually demonstrate afterwards.

Apps and content tied to classes

The institution purchases once and then distributes to classes, year groups or specific devices, pulling those licences back and reissuing them as students progress or leave. Because ownership sits with the school rather than a personal Apple Account, two things follow: your licence spend keeps working year after year, and a departing student cannot take content you paid for with them.

Filtering that follows the device home

Whatever filtering runs on your campus network ends at the gate. Policy attached to the device itself does not, travelling with it onto home broadband and mobile data equally. In a one-to-one programme this is simply not negotiable, because your duty of care for what a child can reach on a device your school issued does not switch off at half past three.

Roles and Smart Groups for a real staff structure

Your academic coordinator, lab technician, librarian and IT lead have genuinely different jobs and should not be looking at identical screens. Delegation gives each of them precisely what their role requires. Meanwhile Smart Groups keep membership accurate on their own as students move between sections, which spares somebody the annual June ritual of maintaining a spreadsheet of serial numbers.

The decision that goes wrong first

Most failed school iPad programmes were decided at purchase, not at deployment.

We have reviewed enough struggling school programmes to say this confidently: the management platform is almost never the culprit. The damage was done in a set of choices made before anybody logged into a console, and by the time four hundred devices are circulating those choices are extremely expensive to unpick.

  • Ownership was left vague. School-owned, family-purchased and genuinely personal devices require three distinct management models. Blur them together and you will eventually apply your strictest policy to hardware a family bought with their own money. The resulting complaints cannot be fixed by your IT team, because the actual problem is a policy decision the school never made.
  • The hardware came from the wrong place. Automatic enrolment depends on devices being registered to your institution at the point of purchase. Choosing a general retailer over an authorised education channel because the quotation looked keener means enrolling everything by hand, and every factory reset drops that device permanently back out of management. Across several hundred units and a few academic years, the technician hours dwarf whatever was saved on the invoice.
  • The teachers were never consulted. Build a policy set that only restricts, with nothing that helps run a lesson, and staff will route around it inside a month. If a teacher cannot manage their own classroom without phoning IT, usage tails off quietly until nobody can defend the spend at the next budget review.
  • Wireless was sized for the old world. Four hundred iPads pulling a major app update at once behaves nothing like thirty laptops reading email. We test this before deployment because otherwise it surfaces during the first week of term, in front of the entire school, and everybody blames the devices rather than the network.
Ask us to review the plan before you buy
Why schools ask us

Four reasons an education deployment is not a corporate deployment.

We manage plenty of corporate Apple estates as well, and what separates them from schools has nothing to do with size. Schools operate against an immovable calendar, carry a legal duty of care, answer to parents, and serve users who never asked to be issued a device in the first place.

We work to the academic calendar

You get one usable window each year to build or rebuild a school estate, and it is the long break. So every date runs backwards from the first morning of term: when hardware must be ordered, when network work has to finish, when the build has to be tested. Those deadlines come from your calendar, not from a project plan we invented. Slip into the opening week and the failure happens in front of every parent at the school gate.

Safeguarding decisions stay with the school

How aggressive the filtering is, how much authority parents get, whether devices leave the premises, and what happens the day something prohibited is found on one: those are decisions for your leadership team and your safeguarding lead, not for us. What we owe you is a platform that enforces them dependably, plus a straight answer whenever a control does not actually do what your written policy assumes it does.

We handle student data the DPDP way

Children personal data sits in a more protected category under the DPDP Act 2023, and in our experience parents now arrive with precisely the questions a regulator would ask. So we write down what the platform stores about each pupil, which systems hold it, how long it is retained and who is able to view it. When a parent asks, the school answers from a document rather than from somebody recollection.

Support that knows a lesson is happening right now

When something breaks mid-lesson there are thirty children sitting idle, which makes it a very different ticket from a broken printer. Managed schools get a 30 minutes response SLA and, more usefully, a named person who already knows your estate. That matters enormously when the problem concerns one year group profile rather than a generic fault anyone could triage.

Where this fits

Six Indian education settings and what each one actually needs.

Six settings we work in regularly. The software underneath does not change between them. What changes every time is who owns the hardware, whether it goes home at night, and how much of the day-to-day management the institution wants to keep for itself.

A private school running one-to-one iPads

A device per child is becoming standard in CBSE, ICSE and international-curriculum schools across the metros. What they need is genuine separation between year groups, filtering that survives the journey home, and reports they can produce on the day a parent or inspector asks. What they are working with is an IT team of two people who cannot lose September to manual enrolment.

A multi-campus school group

When a trust runs schools in several cities, the head office wants one console and consistent standards, while each campus wants control over its own devices and nothing else. Delegated roles give you both at once, and Smart Groups organised by campus and year keep the structure correct without anybody maintaining it manually.

A preschool or early-years setting

A dozen shared iPads, tight restrictions, and one absolute requirement: any member of staff can pick one up and have it simply work. Genuinely simple needs, and nearly all the value sits in devices returning themselves to a clean state between uses without a teacher having to think about it.

A coaching institute or training centre

Courses lasting weeks, learners cycling through constantly, and hardware that has to be stripped and rebuilt between every batch. Everything depends on two things: how fast a reset completes, and whether app licences reliably come back for reassignment. A cohort arriving Monday morning cannot be told the tablets will be ready Wednesday.

A university or higher-education faculty

Here we usually advise against this product, which is worth saying on a page selling it. Universities carry serious staff and laboratory Mac estates demanding real configuration depth, and Jamf Pro handles that far better. The exception is a self-contained student iPad programme run by a single faculty, where Jamf School remains the right choice for that programme on its own.

A school running examinations on student devices

Once exams move onto the devices, your integrity controls need to withstand a challenge rather than simply exist: a properly locked assessment mode, proctor visibility where your curriculum body allows it, and a trail somebody can audit afterwards. This is consistently underestimated, and the gap tends to reveal itself during the very first digital exam session, which is the worst possible moment.

The three states of a school device programme

What we find when we assess an Indian school, and what changes.

The middle column is the most common and the most frustrating, because the school has already spent the money. The devices exist, they are managed in a technical sense, and they are still not being used in lessons.
Feature
Managed and used
Managed but unused
Devices without management
Devices configure themselves on delivery
Teachers can control a class unaided
Filtering applies away from school WiFi
Sometimes
App licences recovered when a student leaves
Partly
Factory reset returns the device to management
No, it leaves the estate
Device use is visible in lesson planning
Evidence available for leadership or parents
With effort
Lost device can be located and locked
Parents have a defined role at home
Yes, boundedUndefinedUnbounded
Programme survives the next budget review
ComfortablyRarelyNo
Which platform fits the school

Jamf School, Jamf Pro and Intune, judged for education.

Technically any school could run any of these, which is exactly why the comparison is unhelpful until you ask what shape your institution is. A primary school pushing iPad trolleys between classrooms and a university with hundreds of staff Macs are not answering the same question. And where a school also carries a serious Windows estate, our honest recommendation is frequently to run Intune for staff and Jamf School for students, accepting two consoles precisely because each is far better at its own half of the problem.
Jamf SchoolJamf ProMicrosoft Intune
Built specifically for educationYes, throughoutGeneral purposeGeneral purpose
Teacher classroom control appJamf TeacherNot includedLimited
Parent-facing appJamf ParentNoNo
Exam proctoring on deviceJamf AssessmentNoNo
Depth of macOS managementGood for typical school useThe deepest availableImproving, still behind
Windows devices in the same consoleNoNoYes
Same-day support for new Apple releasesYesYesUsually delayed
Complexity for a small IT teamLowestHighestModerate
Fits a mixed Windows and Apple schoolApple side onlyApple side onlyYes, one console
Best for a primary school with shared iPadsStronglyOverpoweredWorkable, less pleasant
Best for a university with staff MacsOften not enoughUsually the answerIf Microsoft-first
How a deployment runs

Five stages, planned backwards from the first day of term.

The timings assume a summer build for a June or July start. Running this in a shorter mid-year break uses the same sequence compressed, which we do successfully, but it leaves no slack and demands that the ordering decision is taken considerably earlier.
  1. 1

    Assessment and decisions

    A term ahead

    We look at your existing devices, your purchase plans, whether the wireless can carry the load, and which ownership model applies to each group of hardware. You receive a written set of decisions for leadership to sign off, covering filtering, parental control and home use. Nothing gets ordered before those are agreed, because the answers change what you should be buying.

  2. 2

    Procurement and enrolment registration

    Ordering window

    Hardware is ordered through a channel able to register it to your school so enrolment happens by itself, and we get that confirmed by the supplier in writing before anyone raises a purchase order. Devices already in your cupboards are handled as a separate exercise, because anything bought outside the programme needs a slower, more manual route into management.

  3. 3

    Build during the break

    Holiday weeks

    Classes, profiles, restrictions, app purchases and assignments all get built and then proven on physical devices rather than admired in a console. Where you can give us a real lesson plan we test against it, because running an actual lesson is what exposes the restriction quietly blocking something a teacher depends on. No amount of reviewing settings finds that.

  4. 4

    Teacher enablement before pupils arrive

    Final week

    A brief hands-on session for teaching staff covering the classroom tools, and a single printed page they can keep. Of every stage in this plan, it is the one schools cut when time runs short and the one they most regret cutting, because a teacher who is not confident with the controls will simply leave the trolley alone rather than risk losing a class.

  5. 5

    Term-start support, then ongoing management

    Continuous

    The opening days of term get noticeably more of our attention than any other week, because that is when every unanswered question arrives at once. Afterwards it settles into rhythm: enrolling new pupils, processing leavers, recovering licences, applying updates, and one full estate review at a fixed point each year. Managed schools run under a 30 minutes response SLA throughout.

Questions schools ask

The awkward questions, answered directly.

Same foundations underneath, entirely different assumption about who is operating it. The education product treats teachers, students and parents as active participants and hands each of them their own app, while keeping the administrative console deliberately restrained because school IT teams are usually one or two people. The professional product assumes a full-time administrator and trades simplicity for depth: scripting, elaborate configuration, serious macOS management. A primary school with trolleys of iPads belongs firmly on the education side. A university carrying hundreds of staff and laboratory Macs belongs on the other. If you sit between those two descriptions, look hard at your staff Mac estate, because in our experience that is the factor that decides it.

You can, since Macs are supported alongside iPads, and for a school with a handful of staff laptops and ordinary requirements running everything from one console is entirely sensible. The picture changes when staff Mac requirements deepen, meaning elaborate configuration profiles, scripting, complicated software packaging or specialist lab builds. At that point you are pressing an education tool into a job the professional product was built for. We examine what the staff estate genuinely requires before making a recommendation either way, because paying to run two consoles you do not need is a real cost, and so is running one that cannot do half the work.

Policy is attached to the device rather than to your network, which is precisely why managing the hardware beats filtering at the firewall. Restrictions, available apps and content filtering behave identically on a home connection or a mobile network as they do in the classroom. The one thing that shifts is influence, since the parent app can grant families defined authority over evenings and weekends. Where you draw that line is a school decision, and it needs writing down and communicating before a single device leaves the premises. Settle it in advance or you will end up negotiating it individually with every parent who complains.

Not unless you deliberately configure it that way, and for anything your school is legally accountable for we recommend against it. The division we implement in most schools is this: content filtering and app restrictions are set by the school and cannot be touched by families, while controls over when the device may be used in the evening or at weekends belong to parents. Families get genuine authority over screen time at home, which is almost always what they were actually asking for, and nobody outside the school can switch off a protection the school will be answering for.

They will work, but permanently less well, and the reason is worth understanding precisely. Hardware never registered to your school can still be enrolled, only it must be done by hand, device by device, and that enrolment does not survive a wipe. So the first time a student resets an iPad, whether out of curiosity or frustration, it drops out of your management completely and someone has to enrol it again manually. Multiply that across a few hundred devices and several academic years and the recurring cost becomes significant. A few routes exist to pull some existing hardware into the programme through an authorised reseller, and we check whether yours qualifies rather than writing it off.

Configuring the devices is the quick part, since zero-touch enrolment means three hundred of them build themselves simultaneously rather than one after another. Realistically: two to four weeks of elapsed time for decisions and design, which depends on how quickly your leadership responds, one to two weeks to build and test, and a few days for the physical work of labelling, cases and trolleys given enough hands. What actually determines your go-live date is none of those. It is hardware delivery, and that is why we press schools to settle ownership and procurement a full term earlier than feels necessary.

No part of a school device programme is underestimated more often, and none fails as publicly. Thirty laptops reading email bears no resemblance to three hundred iPads pulling the same app update in one period. The numbers that matter are client density per access point and real capacity in the specific rooms where devices get used, not the reassuring coverage map on a floor plan. We survey before deployment for one reason: a network failure in week one will be blamed on the iPads, and once a staff room has collectively decided the devices do not work, no amount of subsequent evidence will change that view.

You do, and it is genuinely foundational rather than an add-on. Apple School Manager holds your institutional account, the Managed Apple Accounts for both staff and pupils, every device registration, and all app and book purchasing. The management platform connects into it and relies on it throughout. One clarification we find ourselves repeating: the April 2026 Apple Business consolidation did not touch Apple School Manager, which continues as the education service. Several schools have arrived worried after reading about the business-side changes and assuming they were affected.

Arrivals are easy. Add the pupil, the device enrols into their class, and whatever apps belong to that year group appear without anyone doing anything. Departures are where schools consistently lose money, and quietly. Skip processing a leaver and their app licences remain allocated, their device may linger in a class group, and after a few years an institution can be funding a genuinely surprising number of licences attached to children who left. So we build leaver handling into the weekly routine rather than saving it for an annual tidy-up, because an annual tidy-up is the task that gets deferred every single year.

Technically yes, within a class session on managed devices. Whether it is acceptable is a policy question, and it should be answered before the capability is enabled rather than after a parent asks. The position we recommend to Indian schools: screen visibility applies during lessons on school-owned devices, is disclosed clearly in the acceptable-use policy parents sign, and does not extend to evenings, weekends or family-owned devices. Documented and disclosed, it is straightforward. Undocumented and discovered, it is a complaint, and given the care the DPDP Act expects around the data of children, it is a complaint the school does not want.

The DPDP Act 2023 applies to personal data generally and treats the data of children with particular care, including verifiable consent from a parent or guardian for processing it. For a device programme the practical implications are: know what data the management platform holds about each pupil, know where it is stored, keep it only while the pupil is enrolled, and be able to explain all of that to a parent who asks. We document this as part of deployment rather than leaving the school to reconstruct it later, and we keep the data footprint of the platform as small as the programme allows.

If your staff run Windows and you have a small number of iPads, probably not. Intune can manage those iPads adequately, and adding a second platform for a handful of devices is not a good trade. The calculation changes when the iPad estate becomes a real programme, roughly a class set upwards, or when the classroom controls matter to teaching. At that point the honest answer is often two consoles: Intune for staff Windows devices and Jamf School for the student Apple programme, because each is substantially better at its half than either is at the whole. Commercials are quoted per institution, and enquiries get a reply within 4 business hours.
Term-start readiness

Fifteen checks before the first day of term.

We work through this list with every school we deploy for. The first group has to be right before devices are ordered. The second is the holiday build. The third is what stops week one turning into a queue outside the IT office.

Settle before you buy

  • Is the ownership model written down for each device group?
    School-owned, family-funded and bring-your-own need different policies and different consent.
  • Is the purchase going through a reseller who can register devices to your school?
    The single most expensive mistake to correct later.
  • Has the wireless network been sized for simultaneous device use?
    Density and client count, not just coverage.
  • Do you have an acceptable-use policy that parents have actually signed?
    Required if devices go home, and the anchor for every later conversation.
  • Has school leadership agreed the filtering position?
    IT should implement that decision, not make it.

Build during the holiday window

  • Class and section structure imported and current
    Stale groups in the first week create days of manual corrections.
  • Apps purchased and assigned per year group rather than per pupil
    Keeps licences recoverable when students leave.
  • Restriction profiles tested on a real device, not only in the console
    A profile that looks correct can still block something a lesson needs.
  • Teacher app rolled out with a short training session
    Thirty minutes here removes most of the first-term tickets.
  • Charging, storage and trolley logistics decided per room
    A management platform cannot solve a device that is flat.

Ready for week one

  • A tested process for a lost, stolen or broken device
    It will happen in the first fortnight. Decide now who does what.
  • A named person who can reset a student device the same day
    Escalating every reset to an external supplier does not survive the first month.
  • Spare devices configured and held ready
    A pupil without a device in a device-led lesson cannot take part.
  • Reporting you can show leadership or a parent on request
    Coverage, filtering status and compliance, exportable.
  • A defined point in the year when the whole estate is re-checked
    Drift is guaranteed. Catching it deliberately is much cheaper than finding it.
Related reading

If you are still deciding.

Apple device management India

The wider picture: how Apple estates are managed, what the enrolment programme does, and how the pieces fit together.

Learn more

Apple School Manager

The Apple service underneath every school deployment: accounts, device registration and institutional purchasing.

Learn more

Jamf Now or Jamf Pro

The adjacent decision for small organisations and the corporate side of a mixed institution.

Learn more
References

Official documentation

Next step

Tell us the term start date and we will plan backwards from it.

A short conversation about device numbers, ownership model and what your teachers need is enough for us to tell you whether Jamf School is the right platform for your school, or whether something else fits better. We would rather say so early than deploy the wrong thing well. Enquiries answered within 4 business hours.

Book an education device reviewExplore Apple device management