Apparently students have been logging onto the instructor stations in classrooms to do assignments, and then abandoning them resulting in an upset prof for the next class since the machine is locked. So after digging around with W2K resource kit, adding a script on one of the domain controllers running as a domain admin, and a proxy script on a real web server managing what people are allowed to do, most of the work to allow any of the Help Desk workers to log off locked machines in public areas is done. Now I just need to figure out a way to track idle time and if a machine is idle and a user is logged in, execute the script automatically. That one should be more interesting... Since yesterday I decided on the name for the new list server - Jue - I also tried to set that up today. I say tried since apparently we have another machine that likes to reboot randomly. It won't even make it through the install all the way... :( Changing BIOS settings doesn't seem to help, so tomorrow is hardware troubleshooting day. The voltages on most of the lines were slightly high, but probably within spec - within 1/20 of a volt or so. They were consistent where most machines seem to have some high some low and shift a slight bit, so it's possible that's it. Probably the easiest thing other than RAM to swap out too. Hopefully it's not something like the motherboard or CPUs though. :( At least it wasn't tons of little projects today...