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.
The amount of rebooting needed by Windows is idiotic. I just installed Norton SystemWorks. After installing, I needed to reboot. Since I am used to the way Windows works, I expected this. But I was told to reboot a second and third time after running Live Update. That is ridiculous. It wasn't a yes/no choice either just click OK and boom.
This is an application problem, not a Windows problem. The list of things in Windows that actually _require_ reboots (rather than just ask for them as a matter of course) is about as long as the list for any other OS. 9/10 times only a logoff/logon sequence is required, if even that.
I have no problem rebooting to replace critical system files but having to restart for a webbrowser upgrade is uncalled for.
True enough, but you have to remember where the target audience of the bulk of these patches - normal people. These users don't know how to restart services (or even what services are). They don't understand that if you replace a system library that a few running applications rely on, those applications must be restarted. It's far, far easier (and saner) to tell these people to just reboot, rather than "restart your applications" or "log off and back on again".
Really, reboots aren't that big of a deal. You shouldn't be applying patches outside of maintenance windows and services that require 24/7 availability should have automatic, redundant backup systems such that the machine going down - for any reason - doesn't affect the service.