Students being silly s*ds in Google Meet lessons - Can you lockdown more?

[TMBS]

Hi

 

We have students playing silly s*ds in class Google Meets, either trying to gain entry with a personal (Fat Sl*g) email, or using another students details to gain entry and post silly chat comments. I know you can deny users but it pops up and pings which disrupts the lesson.

 

I've locked it down as much as possible in Google Admin, so students can't make calls. I've told staff about Host Controls and we reset passwords if students have been hacked by other students.

 

Anything else we can do to lock down? I appreciate it's all new and will hopefully calm down but it does disrupt classes.

 

Thanks

[ibpalle]

As the Google Meet won't work with HTTPS inspection it's a bit of a problem. It is possible to block google meet completely at specific times which might be useful but if it needs to be available and being misused during that time the filter can't see the content. The cloud filter extension, if you are using Chromebooks might have better luck as HTTPS inspection is not needed when using the cloud filter extension.

[BlueScreen]

Get your teachers to start using Google Meet nicknames and share those with students. Only people who are in your G-Suite domain can join a meet using the nickname.

 

If you're syncing G-suite with a local AD domain, you can suspend an account through the G-Suite admin console and it will unlock itself during the next sync (use it to stop the disruptive students rejoining if they're kicked out). If a teacher requests we block access to a student, SLT and the HoY arrange a video or phone call with the parent of the student on the same day to have a discussion about expected behavior.

[DavR]

+1 for nicknames, it's my preferred solution for Meets. It also has the added benefit that once you end the meeting, students can't go back there and loiter on their own unsupervised, like they can with the classroom-attached Meets.

 

Still no options to disable chat comments in Meets I see, despite it being repeatedly requested!

[dhicks]

Get your teachers to start using Google Meet nicknames and share those with students. Only people who are in your G-Suite domain can join a meet using the nickname.

 

We're using Meets attached to Classrooms, which seem to work nicely - as you say, only domain members can use the nickname, so even if a pupil from outside the class gets hold of the nickname URL we'll be able to tell who it was. Pupils ejected from Meet sessions can't then re-join that session, they have to wait until the teacher closes the session and starts a new session. Sessions only seem to get terminated up to three minutes after the teacher (or last pupil) has left the live session, so more cunning pupils have been able to sneak back in for some un-supervised chat after the teacher has gone. Our advice to teachers has been to make sure all the pupils have left before closing, ejecting them at the end if neccesary, which has caused some confusion with pupils being ejected from live sessions and not being able to get back in, but that's just something for people to get the hang of.

[paulkerton]

so even if a pupil from outside the class gets hold of the nickname URL we'll be able to tell who it was.

They could still copy/paste the URL from the meeting and send it to external users to knock.

They'll still need a Google account to knock, and the knock is only seen by staff, so it might be disruptive but two rejections and it should be over.

 

Unless they have multiple accounts and are determined to cause problems.

Kids are also... "unthinking" enough to send that URL out via Gmail, so it might be worth checking Vault for that URL being emailed out too.

[dhicks]

They could still copy/paste the URL from the meeting and send it to external users to knock. They'll still need a Google account to knock, and the knock is only seen by staff, so it might be disruptive but two rejections and it should be over.

 

Indeed - we've had a few classrooms have external users turn up and try and get in, our suspicion is that a pupil is posting a live URL to their friends. We've had a couple of external users manage to get in to lessons, probably by the teacher hitting the "accept" button by accident.

 

There's a domain-wide setting to allow external users to try and join Meet sessions, now turned off by default, you have to request Google to turn it on for you. We could do with that being a per-OU setting that we have admin control over.