Good idea!  We definitely could use Ghost to propagate a good image.  We in fact did so to an extent last summer for Entrepreneurship, and stored the images on a desktop machine pressed into service as a Windows Server 2003, which now is in the shared Library Office as their Athena server (catalog / circulation system).  

If you get caught up in other matters and are eager to get started on this, you could do that by arranging with Mr. Ruffin and/or Russ to set up a computer (of the predominant model of Dell) somewhere it won't be in use by students yet will be close to a network port so it can be remediated and Windows-Updated (and will be handy if we go the network/server method).  But keep it off the network, physically unplugged, except when you are working on it.  Get it set up with a clean desktop and correct suite of programs in use at the school, OTS remediated, local users [including a backdoor  admin user called CUIP with password that Russ or I will tell or send you] -- I'm sure you know what i mean, getting the computer set up to be just-so.

Please don't go any further than that until we can pull this group together for a little planning, and details you may not have run across yet -- such as how to use Sysprep and why we need to....  Here's a quicklist of some decision points:
<ul>
 <li> How would a re-imaging system be used in the school?  set-up of these units being pulled out of storage?  Emergency "repair" of recalcitrant misconfigured machines already in place?  General periodic site-wide reimaging?
 <li> Full Sysprep or only the little SSID-changer tool?
 <li> Network+server image storage, or portable HDD, or both in some mixture?  [BTW, thanks but we can't use anybody's personal portable drive for this -- ideally the school already owns one, or would buy one (or the two schools could go in on this together) -- failing that, CUIP would bring in one of ours.)  I tend to like the network+server idea, despite being slower than USB 2, just because a whole server is less likely than a portable drive to be misplaced or loaned-out or get stuck onto somebody's desktop computer as a "temporary" storage expansion unit :).
<li> Stick with generic and simple setup of bootdisks, so that anybody who has been shown it before or has the simple printed instructions can use the system; or go for an elaborate setup which automates some of the input and seems to make it easier for the users in the short term but is actually somewhat fragile?
 <li> Would Leadership and Entrepreneurship want to participate jointly? 
</ul>