Best practices for computer lab deployment?
We're evaluating a K1000 and K2000. What I've been testing is using the K2000 for OS scripted installs only (currently Windows 7 64bit) including naming the machine (we've got some adapted postinstallation tasks to grab the hostname from a file based on MAC address), then letting the K1000 install software based on smart labels and also doing updates (replacing our WSUS server in the process). With this setup, I'm envisioning only needing a few scripted install types on the K2000 (win 7 32/64 bit, Max OSX).
What I'm shooting for is having a technician go to the K2000, select a Lab of computers (via a k1000 smart label), tell it to image the computers, go home, and return in the morning to a lab that is completely ready to go for students (OS installed, fully up to date, expected software installed).
Is this something other people are doing already?
Is there some best practices on this anywhere?
Is there anything that we need to do on the K1000 prior to kicking off a lab for reimaging? My concern is that if the computers already exist in the K1000 and it thinks the computers already have the software installed that it may not install the software. I don't think this is the case, but I've been running into some issues in my testing.