jthompson

Am I right in thinking that the option to forget an SSID is only available in the Settings app or via Control Panel? If so, blocking access to those for students may solve your issue.

The sign-in page for lots of Google services, including Classroom, uses accounts.google.com. I can't think you'd be wanting to block it. I should think it also has a tonne of other URLs constructed from it, so that even if someone is already signed in, a link from a Classroom notification email will still want to go via accounts.google.com.

Google Calendar does have some print options. For a whole term, the best option might be to go to month view and then selet print from the cog menu. Pick your date range and deselect the option to include weekends, if appropriate. It'll run to a few pages, but settings the print output to 4 pages per sheet might help there. Not super great, but easy enough to roll off future copies if any calendar events get added, removed or changed. Seems like a shame to have to print out an online calendar, though, but I get that people still might want it on a wall.

I found the live stream of the lying in state somewhat fascinating. I checked in on it at various points throughout (often in the middle of the night oweing to other factors), for a bit of people watching. I also caught the very end of it at 0630 on Monday and am of the opinion that the ending of The Queue is perhaps it's most underrated aspect: the know-how involved in pulling that off has to be world class, surely? The last member of the public passed the Queen's coffin at, I think, 0631, with the various ushers and officials melting away with them to deliver the poignant image of Black Rod leaving the Queen and her guards alone in the hall. The decision to stop admitting people to the start of The Queue must have been taken many hours previously, and yet the last member of the public was ushered past within seconds of the 0630 end time. They avoided admitting too many people to The Queue (thereby overrunning or having to turn people away after they've already queued for hours) and yet managed to control the flow of people such that The Queue didn't empty too soon (bad look), and in fact ended at just the right moment. That's a hard problem. A bit like the fine control needed to bring an orbiting spacecraft safely back into the atmosphere and into the right patch of ocean for recovery. America may be able to do space rockets (mostly), but Britain appears to have the best queue management expertise in the world. Try it elsewhere and people will probably start getting angry, crushed, mugged or having to be teargassed.

It was the student's phone. As in, "please sir, will you take a picture of me and my friends in our cool new uniforms?".

After first encountering BeReal over the weekend (an article about office workers carelessly sharing photos of their confidential work emails), I'ev had it pop up on the radar here in school. A member of staff was asked by some students to take a picture of them. Said staff member obliged, not realising that the phone would take a picture in both directions and post it to a social network. The USP is that everyone on there gets simultaneously prompted to take a picture of what's in front of them, and it will snap their face at the same time. Registers pretty high on the naff-ometer, but perhaps one to have a peripheral awareness of as it relies on diminshing people's agency in deciding whether or not it's a good time to take a photograph and share it online.

It sounds like you need to set a longer grace period for new users. Admin > Security > Authentication > 2-step verification > select the relevent OU Under Enforcement, look for the setting "New user enrolment period". When a new user account is created, that's the period of time during which they'll be allowed to sign in without 2sv enabled. After signing in, they'll be presented with the 2sv enrollment wizard that they can either work through or dismiss for later. After that period, they'll just get what you've reported: sign-in refused unless backup codes have been generated by an admin. Bear in mind that it's from when the account is created, not when the first sign-in attempt is made. You may therefore want to set it to a week or two, something like that.

There's a plugin for GLPI called Addition Fields which I'd highly recommend if you're using GLPI. As an example, I've used that to add fields for recording the date of projectors' last filter clean, so that we can run a report for any that are due to be cleaned. I've also used it to include information about each classroom's ceiling structure and projector mount. Nice and powerful.

I think that's what you call 'putting in a shift'. What a remarkable life's work. How many rich, famous and powerful people must she have met in her lifetime? Every single one of them, whether a President, Prime Minister, multi-billionaire or movie star, will have been the less famous, less respected, minor party in those encounters. It's hard to believe that one woman could so quietly outperform the entire world's supply of ego, ambition and malice. I do wonder whether history will just carry on calling her The Queen.

Have a search for threads on here about student username conventions/formats. There's a balance to be struck between usability (i.e. not too complex), uniqueness (avoiding clashes) and not exposing too much information if the accounts are to be used around the Intenet (i.e. not giving away a pupil's school, year group full name and midle initaals). Having some kind of cohort element in usernames will massively reduce the scope for username clashes if you're combining that with lastname and first initial, without being cumbersome for end users. We also include a couple of digits from the pupil's admission number. That reduces the scope for username clashes to near zero, and has the added benefit of preventing staff from 'guessing' at email addresses: they have to work from the email directory.

Yup, that all sounds like sensible advice, tbh. Using the Google account in Outlook desktop app via Oauth is proba about as far as I'd want to allow, but even then, you end up with calendar invites going all over the place.

I would just use a recipient address map (finance@ mapping to user@), but enable to option to also route to the original destination. Each mailbox would then receive its own copy of any messages coming into the finance@ mailbox. Alternatively, if you need to be more selective on which messages are affected (e.g. only those from a particular sender), you could create a content compliance rule to do that. Define the message matching conditions, and then further down will be an option to add additional recipients.

You would need to add Office 365 as a new host in Gmail: "Admin > Apps > Google Workspace > Gmail > Hosts". You can then use that in a rule in "Admin > Apps > Google Workspace > Gmail > Routing > Routing".

Have a look at setting up split or dual delivery routing in Gmail. Essentially, for certain users, their messages get routed on to some other web server. The documentation is written with an on-prem mail server in mind, but I should imagine it would be possible to route onto Office365 instead. https://support.google.com/a/answer/2685650?hl=en&fl=1 Others on here may have more direct experience of doing this.

Admin > Apps > Google Workspace > Gmail > Routing > Email forwarding using recipient address map. If you're wanting to forward all messages, then setting up an address map there will do it. In the rule that you create, you'll want to leave the option "Also route to original destination" unticked.

If it's a trolley full of USB-C chargers, will they not already be doing something smart once devices are at 100%?

Ditto. Regularly going in and out of sleep is how MS expect Windows to be used these days, it feels to me. PCs and laptops are the one part of the IT estate that can look after it's own power management quite well. It's all the other stuff that needs more effort. Scheduling the powerdown of switch ports for phones and APs out of hours sounds quite interesting, although I think I'd have concerns about running those devices in ways that they've not been built for. If you were to keep APs running, but turned off their radios, would that save much energy?

Email-based ticketing all the way, so use one of the free cloud-based systems already recommended. You might worry about the lack of structured data (location, problem type, etc.) but tbh that kind of stuff will naturally work it's way into people's requests. If not, you have the option to reply to the ticket to request further info. People can also attach screenshots, which they won't be able to do with a Google Forms approach.

I suppose you could copy them from the Shared Drive to local storage and have the desktop app monitor that local folder for then uploading to Photos. Given the volume that you've got, doing that in chunks would be advisable, certainly to begin with. The Photos web app has an option to 'upload' from Google Drive, but I wouldn't be surprised if that struggled to cope with very large numbers of files and folders.

Just to follow on from that, I'd also recommend being a bit of a terminology pedant when it comes to talking and writing about Google stuff. It can feel quite clunky to be writing Google Classroom class, Google Calendar calendar or Google Docs document several times in an email, but I reckon it does help to eliminate ambiguity for people. Google like their obvious product names, but it does mean that you have to be careful when writing any guidance or instructions.

I would recommend sign-posting your users as much as possible to Google's online documentation. It's well written, nice and concise, and aimed at end users. More importantly, it will remain current with the latest features and changes. https://support.google.com/a/users/?hl=en

Like most people, you've spent too much time developing things like empathy, and a moral conscience, rather than spending your time learning how to be an extreme sociopath.

As a slight tangent to this, File Server Resource Manager could be used to prevent the storing of specified file types on network folders. If zip, bat, etc. were the restricted file types, any user attempting to rename a file to use one of those extensions would be denied from doing so. A setup where AppLocker prevents students from executing anything in locations that they can write to, and the locations that they can write to are also largely covered by FSRM, would mean that you needn't worry about them sneaking zip files in disguised as txt.

Yes, if you wanted to discourage children from cycling anywhere, make it illegal to ride without insurance, safety equipment, a cycling license (requiring both a practical and a theory test), vehicle tax, registration plates and an obligatory annual roadworthiness test of your bicycle by a registered tester.

Everyone knows that it's Google who will be summarily deleting those when they find them