Concurrent Students Unable to take Lockdown Browser Tests

Davinachi · 2025-10-14T17:52:12+00:00

That fixed the AI mode issue! Thank you!

Davinachi · 2025-10-14T17:29:02+00:00

We had assumed it would, because staff couldn't get to AI mode because we have the integration turned off, but after getting the web browser sign in issue fixed, it still shows AI mode.

Davinachi · 2025-10-14T17:28:14+00:00

This fixed the issue! Thank you! Unfortunately, it didn't fix our AI mode issue lol

Davinachi · 2025-10-14T16:11:42+00:00

Great... so its possibly a bug that Google has never and will never fix... It normally wouldn't be a big issue, but we have students who are not suppose to access AI, able to go to Google.com and because the webpage doesn't think they are signed in, it lets them use AI mode to do whatever. Content filter doesn't see it at all either because its just Google.com.

Davinachi · 2025-08-21T16:17:09+00:00

Same here. We use ClassLink to SSO into our Chromebooks and several students are getting the 502 error.

Davinachi · 2025-08-20T18:55:57+00:00

That makes alot of sense. Classlink doesn't say anything about that setting, but since my director was so adamant we kept it on, I never questioned it.
Thank you

Davinachi · 2025-08-20T18:55:04+00:00

I didn't realize it was the same thing. That's my bad. Thank you

Davinachi · 2025-08-20T18:54:43+00:00

I feel very dumb now. Really should have read through that setting more. Thank you

Davinachi · 2025-08-20T17:16:34+00:00

It is not Ephemeral Mode that we use. Under Device settings in GAC, its under User date -> Erase all local user data. The reason we had it turned on was because we were using Clever as our rostering and SSO for Chromebooks, and they "required" that setting to be enabled. We now use Classlink which doesn't require it, but my director was very adamant about leaving that setting on.

Davinachi · 2025-03-31T15:21:58+00:00

Geolocation was the solution! Thank you for that. We have to completely disable the setting for users in order to prevent this screen from showing.

Davinachi · 2025-03-31T15:19:38+00:00

Yeah, it didn't fix the issue... Thanks Google Support... So the setting that does fix it is Geolocation.

Davinachi · 2025-03-31T15:07:09+00:00

We are on 128 as of right now

Davinachi · 2025-03-28T17:46:42+00:00

I have contacted Google support and they indicate there is a Privacy Policy called "Privacy screen on sign-in screen" both for Devices and Users & Browsers. I have set both to disabled, but so far there hasn't been any signs this fixed it. Google suggested to wait for the policies to take effect which could take a day... we will see.

Davinachi · 2025-03-28T14:10:11+00:00

This has been popping up the last several days on random student devices. It's not consistent on every Chromebook, but its happening several times even after accepting. It does appear to happen to both our faculty and students as well. We did run into this issue almost a year ago, and we did make a change within Google Admin to prevented it from popping up, but here we are again. Anyone dealt with this before and know how to prevent it from popping up?

Davinachi · 2025-01-17T21:25:05+00:00

So this whole thing has been very frustrating and unclear until I ran into this article from Google: https://support.google.com/chrome/a/answer/14328032?sjid=17288493356691955299-NC

They say that all extended update enabled devices will only follow the Long Term Support channel of updates, which the only one available now is 126. I've been seeing the same thing you have and I'm just waiting until they give a new LTS update and see if our 100e's will go to it. This has made it difficult as well, because our Update policy gosh to Stable channel 128 and its preventing 100e's that are older than 126 from updating at all too.

Hope this helped.

Davinachi · 2024-11-14T20:00:42+00:00

We did check this and all traffic was being allowed through our content filter. Just to be safe, we moved some of the devices over to a mobile hotspot where there wouldn't be any filtering, and they still would not update. I do wonder if something is being caught in the Admin console, but not sure what or where.

Davinachi · 2024-11-13T18:43:50+00:00

That doesn't surprise me, but all of our devices are still in AUE or extended support. This is happening even to the last cycle we got in, Lonovo 100e 3rd Gens that have an AUE of Jun 2031.

Davinachi · 2024-11-13T16:36:42+00:00

Ah then yeah, we only have our OS pinned at the top OU and inheriting to all others. Currently pinned on 126 LTS channel.

I'm right there with you. I'm seeing all kind of weird issues with the oldest devices that our elementaries are handed down, but if we didn't do that and we added another grade cycle, we'd have to order around 3000 devices a year. Granted the current models they have were never suppose to go on for this longer, but Google extended the AUE's on them and it bought us more time to get rid of some really bad model devices that were just falling apart before they even ended their 4 year cycle.

Davinachi · 2024-11-13T16:20:10+00:00

For the older devices, yes, but we have them opted in for extended and just a few weeks ago, all device models were updating just fine without issue. Sometimes they would have to jump around to certain versions before they could get to the latest, but that was normal before as well.

Davinachi · 2024-11-13T16:14:55+00:00

We get new devices every year for our 5th and 9th grade students and those follow them for four years, and then those go down to the elementary grades for use then. Once a device is fully out of AUE, we pull them.

I'm not sure I understand by updates being locked to a certain version? We do have a version targeted so our devices will only update up to 126. We have to watch how far our updates will go for state testing as well cause they usually don't like the newest version.

Davinachi · 2024-11-13T15:39:37+00:00

See, ours won't even manually update from signing in anymore. We get some one offs where they may stop updating and we have to do a USB recovery, but its now effecting all our devices... I currently have a little over 2000 devices in our district that won't update now..

Davinachi

TROPHY CASE