Well, I will have to step in, after experiencing the wonder that is Windows 2000 for the past year and a half.
Yes, it is fairly stable, once you get it running. I almost never get the crashes I got with Windows 98, or even Windows NT. The only other positive thing I can say about it is that they did think out the administrative interfaces much better than in Windows NT. (I have no experience with Windows XP, so I won't even go there).
But, these are about the only positive things I can say about it. In practice, it may be fine as a server, but as a workstation, it suffers from even more "performance degeneration over time" (that classic Windows problem) than Windows 98 or NT put together.
For example, take Internet Explorer: when I first installed IE 5.5, it opened just as fast as on my Windows 98 or NT machines. Now, after a year of use, whenever I open IE for the first time, I wait for as long as 40 seconds for it to open a window. And that is with "about:blank" as my home URL!! If I were to use the classic MSN home page, I would wait for over a minute for IE to even allow me to hit the Stop button, so I could go somewhere else. And the more I use IE, the slower it gets. And, of course, once you have about ten IE windows open, each new window takes agonizingly more time to open.
In fact, the more I use Windows2000 in general, the slower it gets. I have at least 3 times the hardware power of my last NT machine, yet it seems I am waiting even longer for my programs to open.
Now Windows 2000 has been stable for me, because I chose my hardware conservatively, and didn't change things once I installed. On the other had, everyone I know who has tried to upgrade or change hardware, etc... has had nothing but nightmares from Win2000. My father, for example. He is not an IT wizard, but he is the typical "power user". He builds his own computers, he installs everything himself, etc... This was generally no problem, when he was using Windows 95 or 98. But since he moved to Windows 2000, I have spent more late nights helping him fix his videoconferencing, or his TV card, or the networking, what-have-you... I would estimate that Windows 2000 has cost more of my time than all the other OS's my father has used in the past, from DOS, Windows 3.1, on up. And, the problems were never as easy or obvious to solve. If anything, the error messages have become even more criptic. So, I can just imagine that for a large IT department, Win2K has been a nightmare.
Of course it is the independent consultant's dream, since it requires so much time-consuming tweaking, updating, rebooting, etc... Independent consultants--don't take offense; I have been one of you many times. But the question you should ask yourself is: are you part of the solution, or part of the problem? For example, do you push for the latest Microsoft products, even when customers don't need them? Many companies have just finally gotten all the kinks ironed out of NT, and they were finally happy. Then they are convinced to upgrade to Windows 2000, and for what purpose? Do you present the alternatives to your customers, even if those alternatives might mean less work for you?
This last one is a sore point with me. I get laughed at by MCSEs for recommending an open source Unix fileserver. But, every time I install FreeBSD running Samba for a windows network, my server runs literally for years without rebooting. And there are absolutely no licensing costs. So, the customer benefits in several ways: stability, lower cost, cheaper hardware, etc... To the short-sighted, this might seem like I am hurting my own business, since it requires less babysitting. But, I take the view that I should provide the
best service to my customer, regardless of personal gain. I win in the end, because I provide a solution that keeps them coming back to me. And, I have more time to do work elsewhere.
Take the long view, and both you and your customers can benefit. -------------------------------------------
"Now, this might cause some discomfort..."
(