Windows Search 4.0 on a W2K3 Standard Server really causes problems!

   I know this isn't new or news but good old Microsoft in all there infinite wisdom keeps dictating everyone spending more money to compensate for their "innovation". I mean really, how many people don't know what they are looking for in the first place and then to unleash this, resource sucking, Windows Search 4.0 to remedy it? and now, thanks once again to Microsoft,  Windows 7 and 8 require indexing on the server to add folders to libraries!

   Anyway... I got a call form a customer today saying their computers were not responding and that everything was pretty much dead. I got on the server and lo and behold it was indexing. As soon as I snoozed indexing all the servers started responding immdeiately. I even put in a raid-5 15000prm SAS array in a month or so ago to try and compensate for this Windows Search 4.0 disaster.

   Has anyone found a work-around for this piece of junk Windows Search on a server or at least a way to schedule the indexing so it doesn't index right smack in the middle of the working day?