>>Interesting. Rebooting a Windows Server may be SOP. I can recall the many times I have called Microsoft with a server problem. The first question asked; "Did you reboot the server"? That must be the first item on the script the service "technician" reads. Perhaps it is simply a recording! :)
>
>The reboot culture has to end. I use it. At my day job, the help desk techs use it.

I think the need to reboot originated back in W3.0 days. They wanted everything integrated into everything, and all the apps registered (this way or other) at the system level. And they never made the system able to reread its settings, they always have to reboot just in case. In W3.x days it was no big deal - close windows, type WIN and there you are.

Though the number of things which require a reboot is getting fewer (remember when you had to reboot when you just switched resolution on your desktop), there's still a significant number, specially in networking area (speaking W2k here, haven't laid my mouse on XP).