I run a community college computer lab with 112 Windows XP workstations. XAMPP is installed on all of them and it was inadvertently deployed in a way that the Apache service automatically launches at each boot. Is there a safe way that a setting can be changed via a batch file, file replacement or reg hack to set XAMPP so no services are started automatically? We use Symantec Ghost for imaging and management and that can push out batch files, (some) reg mods and add, modify or delete files lab-wide.
These workstations currently have two Apache processes running when they're logged in. (I'm still trying to chase down the source of the second, but I suspect it's the new Oracle dev platform we had to add.) The problem is that this is a general purpose lab that runs virtually every site licensed application for a rather large campus (everything from Adobe Creative Suite to two versions of Visual Studio) and the latest batch of programs requested by the Computer Science department has started to bog things down. I don't have a lot of control over what gets installed, but I'd like to reclaim as much of the CPU and NIC as I can. I'm not very familiar with XAMPP itself, but I've gotten pretty good at putting together patches to push out with Ghost.
Any advice would be appreciated.