Hi everyone, I have a project I'm working on that I could use a little thought guidance.
End goal: Give our 12 building librarians an easy way to enable and disable Chromebooks. (it's amazing how fast "lost" ones are returned when they get disabled...)
What I've done: As a proof of concept, I duplicated my own GAM install on a librarian's machine. I gave them three batch files: One that checks status, one that enables, and one that disables. They scan the barcode (ie-serial) and it just works. For example, here's the script of the "status" bat file:
----
@echo off
set /p chromebookserial= Enter Chromebook barcode to CHECK STATUS:
cd datafiles
gam cros_sn %chromebookserial% info status
pause
------
So, as you can see, it's pretty simple. I am using GAMADV-XTD3.
So knowing that the proof of concept works, I wanted to set up a new instance of GAM with limited scope, different account for logging purposes, and have this be able to live on a shared network drive for easy management/instruction/etc.
Because of the simplicity I was looking for, I tried to set this up with Standard GAM, vs Extended GAM. But if I'm looking at it correctly, Standard GAM doesn't do the "cros_sn" command... It needs the "device ID".
So I think I have to go back to Extended GAM for this. However... This doesn't appear to be as "portable", where I could just have it on a network drive for the librarians (and only the librarians) to access. It seems there is more setup to the Extended Version and having some dependencies on the machine itself.
Am I correct? And probably more to the point... If you were trying to solve this, how would you do it?
Thanks everyone for your input.
Carl