enjay

But just like with fingerprinting, if you explain the process and dispel the alarmist rumours, it should be okay. This is partly why we want to use to use our own hardware rather than ask students to enable location tracking in WhatsApp - they give the device back at the end of the trip, and that way they know we're not still tracking them.

That's affordable. The reviews aren't very positive about the battery life, though, especially if we set them up to ping every 5, which I think we'd need to do for this purpose. Every 30 minutes or 2 hours would be fine if I was trying to track my bike or something which once stolen would probably stop moving fairly soon, but a bunch of kids on a hike.

We wondered about that, but don't really want all the kids' phone numbers.

The kids would know they had them anyway, but the ability to disable could is a problem. From a quick Google, it looked like you would get alerted to the "stalker" and could make the tag beep to help you find it, but not disable it. If we said "this is for your safety, please don't disable them", do you think that would help or just give them ideas?!

We're looking at getting some GPS trackers/locators for when kids go off on DofE expeditions and such like. Has anyone done something similar, and what did you use? A lot of the products we've found need subscriptions so are quite expensive. Would Apple Airtags work? Obviously that's reliant on proximity of an iPhone, but in our demographic we're confident any group of kids would have at least one iPhone among them.

Definitely. Our admissions manager literally had that person on speed-dial when we were launching!

Agreed. There is a lot of work to get it set up (by the admissions team, not IT), and it is possibly best starting small. We did Year 12 first, then in-year transfers before a full Year 7 admission.

We've got it here. The Admissions Manager was massively opposed beforehand but has been convinced since seeing it. It takes a bit of setting up, but is definitely worth it. The name check as it imports students and parents is nice, so you don't end up duplicating a parental contact across siblings.

100% agree. If the Cover Manager's account were compromised, I'd be much more concerned about access to MIS, HR and payroll data than I would about the agency teacher login. Also, the Cover Manager can see everything which the agency account can anyway!

It is an account for agency cover staff who are only here for a day, so the password is emailed to the Cover Manager.

I've just posted a new thread about this, and someone sign-posted me here. Thanks - your script does exactly what I want it to.

Thanks, that's exactly what I'm looking for. @Oaktech 's post /forums/how-do-you-do/233065-resetting-ad-user-account-passwords-nightly.html#post1997734 I spent a while trying to work out why the $cred string wasn't working, then realised the account I was sending from has a $ in it's password!

Thanks @Steve21 I don't quite understand the $RanPaswd line though. Yours is picking one of the passwords on that line (isn't it?) and @dgsmith edited it to pick a word from a list and append a number to it, but I don't see how to create the variable list.

We are looking to set up a shared login which is to be used by agency cover staff who are only in for one day. I'd like to automate nightly password changes on this account, and have that new password emailed to the Cover Manager. We had a Powershell script for this at my previous school, but unfortunately they no longer have a copy. Can any PowerShell gurus help?

Probably looking for your mouse...

Does anyone know if this code is also good for Cubase Elements 13? The e-licenser seems to have been discontinued now, so that's one hurdle avoided.

I suspect that's the case. We notified those schools we knew about due to parents providing screen shots, but I'm sure our parents saw data from other schools too, and it would therefore be reasonable to assume one of your parents could have seen data on one of our students. How many of you have told your parents what happened? We decided not to since we don't know someone saw data they shouldn't have (aka, the ClassCharts defence!), so thought it would cause unnecessary concern, but our DPO did inform the ICO.

I wonder what gives them the confidence or even ability to say most schools weren't impacted, other it being unlikely that bucket-loads of parents would have opened ClassCharts during the 30-minute window of opportunity.

Have they? Hands up anyone who has been contacted by ClassCharts and informed their data was leaked...

Why do you want to know which way I'm turning? It's none of your business where I'm going. Are you a stalker, innit?

I think schools are highly unlikely to get fined based on the actions of their data processors, as long as the data processor had all the right things in their privacy and data handling policies, the school had done their DPIA, etc. That's my understanding. A school as data controller must report "their" breach to ICO, who would then investigate. If ICO find the breach was caused by ClassCharts doing an avoidably stupid thing, there could be repercussions for ClassCharts. I think! It might all come down to our DPIAs and why we shared data with a processor who might do the aforementioned Stupid Thing. Like a lot of GDPR things, I think it will only become clear once someone has actually tested it in court.

It's also a (lack of) awareness of the rules. The driver behind you slows down in response to your brake lights as you approach the junction, but expects you to take the corner at 15mph or whatever, rather than recognising you might come to a complete stop while still on the main road. In some instances (such as the entrance to my road!), things obstruct the view meaning the driver behind probably can't see whether there is a pedestrian or not - of course, they should therefore assume there is one until they know otherwise, but that's not how everyone thinks. I remember my driving instructor telling me all traffic lights are red until I know they're green, and to approach every blind bend as if just round it is a lorry being driven by my mother!

Or nearly getting rear-ended and being sworn at by the driver behind you when you stop to allow a pedestrian to cross the side-road you're turning into.

I think the answer is "sort of"! You don't have to report every incident to ICO, but you do need to document the incident and be prepared to justify why you didn't contact ICO. If ICO disagree with you about it not meeting the threshold, then stuff can happen to you. In this instance, ClassCharts are leaning heavily on being the processor not controller, therefore it isn't there data which was leaked therefore they don't need to do anything. If that is valid, it's mad because it relies on us knowing the incident happened in the first place, which we legitimately might not.

We've included them in WEEE collections before.