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.
System patches and updates should be applied, application updates should be diligently monitored, and the proper filtering and gateways should be activated.
I haven't done any Windows server admin stuff for years, but I remember back in the days of NT4, applying patches and updates used to break stuff. For example, going from SP3 to SP4 caused several sites in IIS to break (for what reason I don't remember). I don't know if has gotten any better since then, but we'd always wait at least 2 or 3 weeks to see how much damage a particular patch caused
Also, the reboot issue is definitely valid here since we're talking about servers, which need to be up and running as much as possible. Why people want to apply it to the desktop also is beyond me.
System patches and updates should be applied, application updates should be diligently monitored, and the proper filtering and gateways should be activated.
I haven't done any Windows server admin stuff for years, but I remember back in the days of NT4, applying patches and updates used to break stuff. For example, going from SP3 to SP4 caused several sites in IIS to break (for what reason I don't remember). I don't know if has gotten any better since then, but we'd always wait at least 2 or 3 weeks to see how much damage a particular patch caused
Also, the reboot issue is definitely valid here since we're talking about servers, which need to be up and running as much as possible. Why people want to apply it to the desktop also is beyond me.