Planehazza

Wish us luck, send flower to my funeral... We've turned a blind eye to iPad student internet tracking for too long. Yes, they've been filtered and tied to 1:1 pseudo accounts, but after I reminded them we were averaging 1.5 alerts per day across the trust and we had no way of tracking who was using any of the 600 iPads, our hand was forced and I've implemented Shared iPad mode, federated against Google. Some staff are very unhappy that it's too hard, but we just have to use Safeguarding to quieten them again. Anyone else been in this position? Teachers spouting safeguarding left, right, and centre, but heaven forbid they have to teach kids IT skills in an IT lesson, using a very simple user guide I created for them...

I guess another way to think of it is you're more likely to get backing from money people to ditch them now.

Oh I don't know real pain. I thought I did, but we're rolling out shared iPad mode across the whole trust, including KS1. Wish me luck. Drinking at work in schools is generally frowned upon, right? Just checking... 😂

Another bump to this but cloudwise are no more I believe, or were bought out or something. I'm in the process of implement Clever at our trust, employing the SSO feature for QR badge logins for KS1 and KS2, which is all free now. It's the MFA you now pay for and it's actually not too pricey.

Honestly it depends on who installs it. We've got it in 8 schools and every install is different. Good luck getting them all consistent, especially if you have more than one domain. Their product was all the rage 5 years ago, but now it's overly complicated and their support is abysmal.

We're going through procurement process in Q4 so I can ask, but I suspect you'll have an answer by then.

Thanks Ben, and for just validating how I feel with this. It's nuts. I'm already a but miffed with these iPads, as we're rolling out Shared iPad for ALL devices, including KS1. It was my idea as we've no other way of keeping them compliant with KCSIE without relying on teachers to keep track etc. They're going to hate them and me, but we've reminded them how dangerous these are when I've showed them we've averaged an alert a day on the current system, and we don't know who uses which device currently... I'm anxious, but content in my choice. OK, so if you'd be so kind, please hear me out... I can have a single default policy that applies to all the names them say iPad-{{serialnumber}} then add the devices to the Site1-iPad All/Site 2 - iPad Students etc groups to which another policy is set with a different template? Them having Site1 etc in the name isn't crucial; what's crucial is easy, quick software to hardware identification for group assignment. Being shared mode, I can't simply enter a pin to go to Settings > General > about and the serial on the back is tiny. Of course this begs the question of asset management - why don't they have tags on them etc. That's another resource/time question...

Yep, ipads. I wonder if I've just misunderstood these enrolment policies then. I thought they applied at enrolment and only then? Surely I don't need to have multiple policies for each batch? It's going to be a lot overhead. I have got 600 devices linked in Intune to ASM. Really don't fancy manually assigning a policy one by one. Ans if these policies override names every time ASM and Intune sync, what is the point in a device rename feature MDM side? Or is there a way to remove enrolled devices from the scope of the enrollment profile once they're on boarded? Sorry I'm either just not understanding something here or this is pure madness?

Yep, we're not currently enrolling any devices and yet the number is now 25 devices. Why is the naming template on the enrolment profile renaming previously enrolled devices? This is madness, and is going to make it mental to manage the devices. I wonder if I need to set up separate sites per school in ASM then have a token for each so I can have different enrolment polices per site. What a nightmare this is, total garbage

Feel like I'm going crazy, but i'm 99% sure the enrolment polict that sets the device name at enrolment is renaming previously enroled devices. I thought I saw it happen at the last school and figured I'd bulk renamed the wrong group. Now at the second site, different site prefix and I'm seeing 20 devices checked in with the new prefix. We've only enrolled 14! Why's it doing this?

I thought about those but the issue I'm having (compounded by the fact we're reluctantly enforcing shared iPad mode KS1 through KS4 and staff) is I'm struggling to find a way to name them in bulk quickly and easily. I'm hacving to go through 600 iPads to wipe and enrol to Intune and am doing it as methodically as I can to leverage enrolment policy naming templates, but it's hit and miss and something has gone and renamed previously enrolled devices too 🤦

Deploying apps is tedious. We have 8 schools using ~600 ipads, and each school requests different apps, blah blah. I have the iPads in nest groups, ie Trust All iPads > School All iPads > School Student iPads > School KS1 iPads Trust All iPads > School All iPads > School Student iPads > School KS2 iPads etc## This way I can block Safari etc. and trust level, or ban settings at staff/student levels once. I've got quite nice targeting options. Deploying an app to KS1 iPads at school 1, then KS2 iPads and schools 2 and 3 etc, is going to take a lot of time especially if we have nearly 100 apps etc. Do you guys take a similar approach to SCCM? Have a group for each app then just add device groups into app groups? I'm just thinking out loud that this will be fast for subsequent deployments?

Formal answer from Lightspeed is no.

I think we're giving them notice they're getting binned. Dire product and support now. I'm praying I can convince the powers to choose SignIn App

I should add that my current work around is an open wifi hotspot with the correct WiFi profile deployed, so I can get them online by selecting the SSID and not entering a password. Still quite slow though