Buzzer90

Are you using Inventry Central? Are they getting pushed out from there as well as the MIS? Or has someone added the staff records manually to Inventry and also getting synced via MIS?

Anyone else get the Internet issue as mentioned by the OP? Just trying to pin down if it is another Senso quirk (we had the issue in v1 that was causing file explorer to crash on login...)

That's because the COO was a slide in front throughout the CTO's speech.. 🙃

The testimonial quote on the home page did make me laugh, it's a fair claim... This is the best thing that has ever been invented.

They quoted us the same initially and then after 'review' reduced it to £300... Whether that was because we were migrating several at once or you can just ask for a review and see what they say.

InVentry charge too if you're using them.

Will staff be moving around or same teacher in same room everyday? Just thinking about the inevitable occasions when staff would leave themselves logged in to their Google account if moving around.

Also looks to be flagging apps.cpoms.net as 'Hacking'... Happy Friday.

Just Google, for whatever reason it's getting flagged under the 'Proxy Bypass' filter list. Browsing to sites directly is fine.

I could be missing something (I usually am...) but can you not just delete the original distribution list and re create it as a shared mailbox?

Back now.

Not using Senso are you? We're having very similar issues and apparently there's a bug with Senso V1 that is causing this according to their Technical Support, I've also seen it mentioned elsewhere on this forum. We're running 24H2/25H2.

Admin Centre been flaky all week.

Had this on a few devices the other day, after updating & then rolling back Office amongst other things to no avail it was just an uninstall & re install of Onedrive that got it working again. Was a fun few hours...

As far as I'm aware the patches are only necessary if you are in an Early Years setting, not needed for some primary and obviously all secondary schools.

Graphics Driver it turns out, had tried updating but needed rolling back...

Anyone got any Latitude 3120's? We've had 12 come into us over the past 2 days as they won't boot to Windows. POST fine with Dell Splash screen but then screen goes 'off' I say that as laptop is still powered on but just a feint blue/purple display. Some really bizarre things like HDD's working in Spare laptops and Spare HDD's working in original laptop but original HDD in original laptop it doesn't like, although it will boot fine in Safe Mode. BIOS updated & also tried rolling back but no joy. Slightly concerning as we have over 200 of these... Thanks

Thankfully had a couple of black toners delivered this morning, still missing a couple more. Could do with a stash of them for the next time it happens....

Still no sign of any Xerox black toners here.

Yup, second lot of supply issues with our Xerox machines via ArenaGroup since September.

We had Toshiba's for a while and not too many complaints with them, moved to Xerox end of last year and it's not been the best experience... Anyone else with Xerox and having issues with Toner supply? Twice in 3 months where we've been waiting weeks for Toner delivery.

Anyone having printer issues again? We seem to be experiencing printers removing themselves and then getting Printer not found when trying to re add it?...

Update. Tested this on one of our clients and seems to fix the errors whilst mapping network printers & hanging when printing. Will try it on a few more. https://support.microsoft.com/en-au/topic/november-22-2021-kb5007253-os-builds-19041-1382-19042-1382-19043-1382-and-19044-1382-preview-d1847be9-46c1-49fc-bf56-1d469fc1b3af https://www.windowslatest.com/2021/11/23/windows-10-kb5007253-21h2-21h1-released-with-these-fixes/

This just not linked to the mess Microsoft have created with their recent updates? We're experiencing the same here with clients not being able to print, crashing app when trying to Print and some getting 'Calling for printer' when trying to print. Only 'fix' so far has been uninstalling KB5006670 on the clients and hoping Microsoft sort their s**t out...