Linked by Adam S on Tue 28th Sep 2004 22:29 UTC
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.
To read all comments associated with this story, please click here.
You get what you pay for either in time or money. The author of that article has one legitimate beef and that is the number of times necessary to reboot the server when patches have to be applied. This is a problem thats plagued m$ for years and should have been addressed a long time ago, but its microsoft so you learn to build your network around such weaknesses.
As an example 2 or more clustered and load balanced servers, connected to a san via. fcp, ifcp or iscsi, would mean for alot better network persistence. Reboots become a none issue- as they should be. Patch one windows box, reboot it and everything keeps on chugging along just fine. Do the same to the others when you are sure you wont have issues with the last one. If you are running GSX or ESX it becomes even easier.
In 7 years I have had to use microsoft's paid support twice. One was for nt 3.5 for an issue I dont remember and the other was an early domain issue with windows 2000 which was primarily my fault for not looking into the new requirements of native win2k domains before jumping right in.
Microsoft still allows you to set seats for client licenses unlike almost every other server product (novell and sgi irix come to mind) that will squeal at you if you go over. And if your users are on windows 2000 or windows xp they dont take up any cals. volume licensing and server deployment and management of client patches is pretty painless if you spend the time to look into it.
Hard to believe no one knows this but you can pull out most accessory applications if you do an unattended install. IE stays though. But considering the default security configuration under 2003 I don't see why anyone would care if its there.
And for gods sake if you are going to have you entire company live in terminal server get citrix metaframe and do some research or atleast do some fact finding with reguards to resource allocations and limitations before you commit to a platform. If you cant find the white papers you need on the win2k3 website try using the "search" window.
In short- do some research. All platforms have their strengths weaknesses and quirks. Its up to the admin to make sure it all works and stays working and you can't do that without doing your homework first.
and just something to note I recently setup an osx server to run extensis portfolio and font server at my office. OS X server also requires regular reboots after patches- you always get what you pay for in time or money.