So, the last two years of our 1:1 has been fun. There is one problem that I have though that takes up a lot of my time and there is no good solution. That is when I give out a spare laptop to a user while theirs is in for repair. These laptops are inventoried for the purpose of being loaners. So, to rather constantly be updating my inventory and constantly reassigning users to specific machines we give out spares.
Next school year I plan on naming every spare with a unique naming convention and then making a smart group of these spare machines. I want to make it so that every 30 days a policy runs that disables all local user accounts, thus forcing the user to come see me for support thus allowing me to get their spare back form them and into my inventory.
I have had students refuse to give me back spares because they don't want to give up their 5 gigs of songs they ripped to them. I also am going to have active search and destroy policies that limit the files being saved on spares.
Basically, I want spare machines to not be as fun as their actual machine so they have lots of incentive to bring me back the spare. I figure I could just loop all user accounts and change their passwords to something ridiculous (random 30 character string) and then force a reboot. They won't be able to log in and they will come see me immediately if they can't log in.
I think this is pretty simple to do, but I would like any feed back from anyone on the list who has done something like this before.
Thanks in advance, and have a good weekend.
Thomas Larkin
TIS Department
KCKPS USD500
tlarki at kckps.org
blackberry: 913-449-7589
office: 913-627-0351
