PotNoodleTech

You've got a point there mav!

Thats very reminiscent of the classcharts data breech?

You shouldnt be needing to use a pupil phone for any school purposes so yeh use your own hardware for sure.

It's a good idea, but sounds like a bit of a health an safety / data protection nightmare - a'la when fingerprinting first came out. Just make 110% for damn sure you got the parents on side with written agreement.

They must be able to write back though otherwise apps like classcharts wouldn't be able to write back AM/PM attendance etc straight into SIMS?

You've got a wonde account username/password for wonde to work - they can write back to the sims database or wonde wouldnt work!

Just bare in mind that if you spend 10 grand on this but then SLT don't follow up each incident then it's a total waste of money, have seen that in a few schools round here.

That's quite the impressive Vlan template Aprice!!

It's not really the systems it's the people - people just don't understand that signing in properly and signing out again could literally be life and death for someone or even a poor firefighter not going home to their family. Until the staff and pupils are *forced* to take it seriously you will always have out of date/incomplete fire registers and basically be muddling through and hoping everything is ok but if there is an actual fire you will be putting people at risk.

In an ideal world you should only have Curriculum and Guest SSID's If you go back to basics, those are the only two types of devices in the school: School owned devices for both staff and pupils = Curriculum Anything that isn't school purchased = Guest.

If you think the keyboard comes out bad on the swab tests try your staff room's dishcloth - It will be surprising it doesn't speak to you when you walk past!

So you've got this thread about constant issues and no reply from SB and yet there actually logged into the forum daily, touting for business in other broadband threads? I'd be miffed if I was a customer.

Just some comments on your main scenario before you implement the wifi as per the several great replies on this thread already: 1 - Domain Joined PCs should all be wired - they don't move so cable them in, this makes them faster more reliable and unburdens your wifi points to serve actual WIFI only devices that may need the bandwidth. 2 - Non domain joined but still internet connected PCs - is a big no no nowadays as they're a rife target for viruses and malware - wipe them join them in to the domain so you can ensure basic security and more advanced cybersecurity compliance and make sure they are hard wired in for reliability etc as above. 3 - Staff personal devices should be treated as guest devices. Basically anything that is school owned is not a guest, anything that is a personal owned device is on the guest network. 4 - Keep the number of customer facing Vlans to a minimum as the more vlans you have the more everything (particularly WIFI) slows down.

Cool - what 3d printer is it - do you want to donate it to a school that uses 3d printers every day bit can't afford them?

Just bare in mind that if it is connected, it can be infected and it can also infect others.

That is a darned interesting idea - I am well out of touch with starlink etc. Time to open youtube!!

Having had Ubiquiti in the past, and Aruba now, I would go Ubiquiti if I was doing it again.

The problem with failover is that if it's all going back to the same exchange which is likely then you effectively don't have failover. As proven by the power cut yesterday evening which looks like it took out our local exchange - we lost power totally to the whole village, but 5 other secondary's and 20 primaries lost their internet too even though they were miles away from us where the power cut actually was? The only other time we lost internet was when a gardener cut through the internet link with a hedge trimmer. Again - your multiple links going back to the exchange through the same underground pipework are both gonna go down so no redundancy in that scenario either.

It seems quite an unusually long list of disparate subject specific equipment you are trying to put it one suite? I mean we have 3d printers and laser cutters, but only in the DT department We have mixing desks lighting desks etc, but only in the drama department We have music interfaces usb keyboards etc, but only in the music department etc Just wondering why all in one room?

If it's got a serial port on it then it's gonna be at 20 years old possibly more! Will likely be a challenge to get running on your cyber security compliant windows 11 hardware.

The google for education offering is approx 1 light year ahead of the microsoft offering - I don't know why but for the last 10+ years MS have spectacularly failed at building a simple easy to use classroom system. (And they've had plenty of goes!) The fact is sharepoint teams etc is all difficult to use for an end user. We still see loads of (adult) people in the LA struggling with teams and sharepoint on a daily basis and yet my pupils with a reading age of 6 are using google classroom day in day out zero problems. You will get people on here saying I am wrong and microsoft are great but sadly I just think they've never been lucky enough to witness how smooth a google school runs.

I was just about to say I bet it's other staff deleting things. You beat me too it lol. It's generally a bad idea to have multiple staff sharing a mailbox as things like this happen and no one owns up to being the one to deleted all on a friday night by accident.

What's the interface like on them? Ubiqs web interface is pretty much the best around as far as I've seen?

If your on a tight budget which I assume it will be given your using 10yr old switches now, then look at Ubiquiti you can't really better the value and performance for the money plus it makes it super easy to add a load of ubiquiti wifi points down the road.

Thinking about it could it be an imaging/build issue? We had our LEA build some PC for us (first time, and last time I ever asked them to). They must have used some kind of cloning software to do the imaging (rather than say, building them individually on MDT) This cloning sofdtware broke the AD links on every PC - and I had to do as people have suggested above, remove from the domain back to local work group, check AD and delete any objects, then re-add to domain from scratch.