Students pulingl power at startup, then breaking Group Policy processing
Oh joy. This has caused some head scratching and stress.
Seems like some of our students with far too much time and far too little sense have worked out a new trick. It involves pulling out the power cable (or resetting the PC, shutting it down however), possibly during logging on. They then restart the PC and log on again - and Group Policy processing (possibly just the user config) hasn't applied. That means no locking down, no redirected folders, etc. Thankfully, with UAC in place and with a robust super-mandatory profile in place (as well as AD users set as User only) they're still only logging on as themselves, but of course they can still get at many things that they shouldn't. Plus, as they're pulling the power it won't be long until I have a wave of corrupted installs. Cue a slew of 'lol i haz admin rightz'.
I know this is a classroom control issue. I have tried asking staff to keep an eye on it. I have some names, but it's like anything that's gone into the wild - we've got loads of them doing it now. We can go the brute force approach and warn them all in assembly etc, but I'm wondering if there's anything I can do from a technical view.
My policies are pretty robust, when things aren't messed with it all works well. The old 'wait for network at startup' GP setting is on (swear this doesn't work in 7). My only thought now is to bodge across the registry changes from the relevant .POL file in the sysvol into the students' .MAN profile hive, if I can - that way, the policies to lock the session down are at least applied. Makes applying changes a real headache though.
This has been a problem for a while though it seems, so I'd like to squash it.