I'd toy with a different approach.
Students often do bad things to them: sometimes lethal for the windows.
This is the real issue. Perhaps the trick here is to realise they will break things and design the system to handle that.
So, the real solution is to stop students from doing bad things to them. Don't give them admin accounts unless needed - and generally reduce their ability for mischief. While its so tempting to use one account for everything, giving students their own account is a good way to ensure they don't misbehave.
But my students actually need root access.
At this point, the best solution is to treat your installations as being disposable. There's a few approaches to this. With windows 7, there's a neat tool that lets you backup activation tokens so you can have one golden image and restore the old activation. This is a pain.
I have a fairly substancial post on installing windows 8 to VHD (and it works on 7 too).
So build, setup, zip up the VHDs and leave them on the same system. Deny your students the main system, and let them run off the VHDs. If things happen, just delete, unzip and at worst, point your bcd at a new vhd.
I'd even considering not activating the systems and just running them in evaluation mode, scripting up rearming them, and nuking them once a semester.