Actually, that is not the case (in my case).
I fix winblows boxen by installing linux on it. I mean, no traces of winblows... left, permanently.
The only exception is winblows running as virtual box under vmware on linux, thusly in safer environment... if someone needs legacy stuff.
The downside of linux is one that I see: the maze of dependencies. Someone has to come up with a better version management and some automated way to fetch the needed dependencies, albeit mandrake software manager is doing a good job provided that the packages are d/l from their repository/mirrors (or from textar --
www.pclinuxonline.com). It is rare that something will get stuck on deps, but it is nonetheless frustrating, especially after dilligently fetching the needed packages from rpmfind site or compiling sources, you'are still stuck because that library need another library that needs another library. Sometimes symlinking the version one has helps, though.
Beside that, after a bit more than one year running linux on my workstations, I would not go back to winblows even if they paid me.
As for server, I was using linux since 1996 and had about 4 reboots throughout that time, all kernel updates and one spontaneous shutdown -- fortunately the server is setup to autoboot after 15 minutes. Happened at 3 am so no one of my clients noticed.