I've been using Windows as a network administrator for just over 6 years now. I've used NT4 servers, 2000 servers, and Windows 2003, and there has been a tremendous improvement with each version. There are still some things that drive me nuts in my job, though, and this is a chronicle of the top five.
Permalink for comment
To read all comments associated with this story, please click here.
The error messages on Windows generally suck. They are often vague to the point of being useless for pinpointing a problem.
Several error messages I've had the pleasure of researching point to several possible problems on both Microsoft's knowledge base and Google. Guess what, half the time none of these possible solutions even work.
Also, the reboot issue really is a problem for servers despite what several Microsoft apologists want to tell you.
The lack of a useful command line is somewhat an annoyance but not crucial as remote desktop is actually pretty decent so long as you don't intend to use it over dialup. Windows Scripting Host allows you to automate a surprising number of tasks as well.
With all of that said, I still prefer to deploy *BSD and Linux given the choice.
The error messages on Windows generally suck. They are often vague to the point of being useless for pinpointing a problem.
Several error messages I've had the pleasure of researching point to several possible problems on both Microsoft's knowledge base and Google. Guess what, half the time none of these possible solutions even work.
Also, the reboot issue really is a problem for servers despite what several Microsoft apologists want to tell you.
The lack of a useful command line is somewhat an annoyance but not crucial as remote desktop is actually pretty decent so long as you don't intend to use it over dialup. Windows Scripting Host allows you to automate a surprising number of tasks as well.
With all of that said, I still prefer to deploy *BSD and Linux given the choice.