I think that your situation is common with Win2K. A lot of organizations spent so much time tweaking NT4 to get it working just right; they are taking a very cautious approach to Win2K as server software.

BTW, the "compelling app" theory is that an OS or hardware will not be generally accepted until there is a compelling application using it. Examples: the Apple II was a hobbyists machine until VisiCalc. The IBM PC really boomed when Lotus 1-2-3 came out. CP/M was the compelling app for S-100 bus computers. Arguably, the compelling app for Windows was/is Office.


>>I am reminded of the attitude that a lot of DOS programmers had in 1991-92 when Windows got popular. Or that Novell network guys had to NT in 93. Ain't too much new DOS or Netware work going on these days.
>
>>Not to say that you might have a point. It's just that new paradigms in our industry seem to hit the "compelling app" point and are suddenly adapted seemingly immediately.
>
>>One of my old favorite IT theories, BTW, the "compelling app" theory. I forgot who originated it but it's pretty much held up for years.
>
>John;
>
>I must agree with you and am still shaking thinking about DOS and Novell. One thing I have to say about Microsoft - I have put food on the table for my family for the last ten years thanks to them. It is up to me to stay on top of any technology changes - and they occur almost daily. If I wanted to, I could still support only DOS pre version 3.3. After all, who is going to want 3.5" floppies? 5 1/4" is here to stay! Gee, I heard people say that about 8" floppies and the S-100 Bus!
>
>Putting our heads in the sand will sure show Microsoft a thing or two! Microsoft might be getting richer with the release of new software but it keeps the industry going. Not everyone wants to jump onto the latest Microsoft Bandwagon - at least not immediately. Our corporation has over 50 servers running NT 4.0. We are evaluating Windows 2000 to be sure it will be compatible with our production applications. Our schedule is to complete evaluation sometime early next year. As one minute of downtime costs us $10,000, we want to be sure of what we are doing. My guess is if we go .NET, it will be about three years down the road.
>
>Tom