Source
r/k12sysadmin•
ZeroAccess

WIDA ACCESS testing Chromebook deployment help

When I first set this up with the old Google admin panel there used to be a spot to just upload the chromeos.json file, which would tell the chromebook what ORG Unit ID to use and they would self register.

I don't know if I don't have the .json correct anymore, or with the switch to the COS-SD nonsense they changed something, but for whatever reason I can't get the chromebooks to register anymore, they have to manually type in the org unit ID. Anyone know why? Anyone want to share what their json field looks like in the "policy for extensions" part of the kiosk app permissions?

Posted Mar 6, 2020, 7:52 PM UTC

117
Peally23•

Glad to know I'm not the only one that hates working on that clusterfuck of a testing system all the time.

4
bmw17•

8 straight years of me complaining to find another system. At some point I just want to build a competiting product that simply works!

1
idontknowu1•

If you still have the json files just open them in notepad and copy/paste the text into the field in the console.

3
[deleted]•

[deleted]

1
idontknowu1•

It shouldn’t have changed. When they updated the interface all it does is shows what the content of the json files were. I haven’t messed with it in a while but you used to be able to download zip files with all the config files for the different architectures including chromeos. Maybe try redownloading them?

2
[deleted]•

[deleted]

1
Sardoodledum•

Could it be the OS? https://www.reddit.com/r/k12sysadmin/comments/f0cdnp/if_youre_using_drc_insight_for_testing_on/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

1
Guaritor•

So... I dont know if this will help or not, but I was working with an IBoss support tech on a totally seperate issue, and he mentioned that he has had a lot of issues with this new gsuite interface, and showed me that a lot of settings that I had set in the new interface, were actually not set when we switched back to the classic interface.

It was weird, but once I set what I needed to in the classic interface, stuff started working, so maybe give that a look?

1
SquirrelSafari•

Mine looks like: {"ouIds":{"Value":["##########"]}}

2
[deleted]•

[deleted]

1
5Vikings3•

IIRC after I added the JSON values ({"ouIds":{"Value":["##########"]}}) my Chromebooks would not register either. When I came in the next day and tried they worked fine. I chalked it up to DRC/COS being slow.

1
adstretch•

I give the test admins the org ID number so when they don’t work properly they can just type it in. Our problem seems to be that we’ve had two different servers with two different org ids and when we changed to the new ID it didn’t over write the old one without erasing the chromebook. So all our newer machine that have since been enrolled work fine but the old ones are still hanging onto the old org ID. But if the test admin has the number they can just add it at the time of the test. No muss no fuss.

1
[deleted]•

[deleted]

1
adstretch•

We test even fewer so honestly automating this is honestly more work for me than it’s worth. I just shrug and give out the number when someone asks why it’s not working.

1