tom_newton

Are these BYO or school devices?

This lot are thoroughly good eggs in my experience: Home | ICT-Direct

Quite possibly going to get the Norway treatment from the super el nino

That's the thing with Apple's hoops - you just gotta jump through them. The system is built for people who actively enjoy colouring inside the lines

Ultimately, shard ipad is going to deliver future benefits (or lack of pain) too - less likely kids will "lose" work, by saving locally and letting the ipad circulate, decent auth brings opportunity, best to normalise it early before it becomes an absolute necessity

Shared ipads would be the route id take, rather than the cumbersome login page

Argh. Off to see my wife in Kenya, I fly out the day before. I am sure you must have told someone here the dates, but I didn't know 😢 Anyway I think you'll get the inimitable Rob Faulkner instead, leaving me 0 for 2 on the last 2 EG confs

(no worries I found it)

There is an update to edge due today - 153 - that we expect to resolve some issues. Can you ping me your ticket number?

Just don't mention "S-month"... if we don't say its name it cant hurt us

It's always been tricky with Mosyle free - I dont think it works super well. You really do need to have students logging in to the ipads properly to use the browser app. If it's non-logged-in ipads you might be better with the login page

Are you mosyle free or paid? Proper "shared ipad" per apple's definition?

Yes, Newport is now out with quite a few customers - no cluster support just yet, but other than that it is there. Hopefully you can upgrade soon!

Yeah, go for it. All I would say is if you are connected to the smoothwall cloud, be careful - because if you have 2 on prem devices with disagreeing configs talking to the same cloud instance, you are going to have a bad time.

He had a good innings

Theres a degree to which "testing the filter is active and roughly appropriately configured" and "testing that monitor is configured and active" are different jobs to "test the technology and prove it catches stuff" - the latter is more a job for UKSIC to make sure the accredited solutions are up to snuff. Being compliant is a combination of picking the right tools, installing them in the right wat, and wrapping that in a layer of policy and process that works for your school.

Testfiltering is pretty useful, moreso when it is run from devices and accounts which don't belong to IT. You would be surprised how many safeguarding issues exist because filtering is missing or misconfigured. Additionally testfiltering now demonstrates wether you've got https decryption (or something equivalent). Again. there are more schools than you'd like to think running filters with no visibility into (eg) google search terms. Having evidence of some regular and frequent testing will certainly demonstrate a broader commitment to considering your filtering rather than set-and-forget.

I'd be inclined to have a couple of testfiltering results from around the school (pref by people who arent IT) recorded each month, and then a yearly "consider your policies, and what needs improving" - a minuted meeting with relevant stakeholders would go a long way to documenting that.

The performance issue with browser versions likely would not be bandwidth restricting (senso is indeed a good candidate for that!) - that should be resolved with the latest update, although there's still a bug in Chrome and Edge on windows that pushes the extension into efficiency mode incorrectly. I believe it is being worked on by the chrome team.

If you have securus web browser that's probably a good start, rather than changing all your filtering round

That's unusual. I'm sorry for that - can you pm me your details so I can see what went wrong? I'm just about to take a week off, so I might be quiet for a bit

I could possibly see it if the traffic ends up terminating in the same place? Like a sort of half baked domain fronting? Apple do allow you very limited access, which is why a custom version of Firefox is part of our arsenal

Smoothwall ipad filter should definitely catch those - as there's a second request made to the real site!

Yes, for the same reason (no auth = dont know who you are) destination auth exceptions still apply to all users - so by definition all users can then access insta. You could... fix IP range of ipads. Dest auth except insta Block insta for all Unblock insta for ipad IPs as a higher priority policy

I'm sorry for that, I am sure there's a cure