hk5754 — Thu, 15 May 2003 23:03:31 +0000

I leave my server on Auto-Update of patches and have not had any problems yet. If I do ever encounter problems, I just let MS fix them remotely. Of course, I have to pay but I let them know they will pay if they screw up my server!

Mark Hensler — Fri, 25 Apr 2003 09:42:10 +0000

I think it's best to have a testing system setup for a production environment. Meaning, if I had a valuable box, I would first install XYZ on a machine with a similar setup and give it the what-for. If it survives, then proceed to install on the live box.

brady.k — Thu, 24 Apr 2003 23:58:30 +0000

good question, i guess it depends whether you want your comp/server to crash from an error or an attack

nike_guy_man — Thu, 24 Apr 2003 22:41:04 +0000

Here's a solution: Get a Mac :-D
I've had mine for over a month now, no 'security patches' none of that
The only update it did was automatically update Quicktime for me

Seriously though, I never had any problems with patches on the multiple years I was with Windows
I have read a lot of reports of patches that don't work though
Is it better to install a patch right away before an attack would take place? Or wait 2 weeks ot make sure it's good and meanwhile leave your server/computer vulnerable??

brady.k — Thu, 24 Apr 2003 21:00:30 +0000

i generally download patches every two weeks, i have yet to have problems, as i dont dl ones that just came out, i wait for them to fix the fixes...just wait a bit after you recieve a notice about one, to make sure it doesnt need fixing too, and you will be fine

Mark Hensler — Wed, 23 Apr 2003 23:21:33 +0000

*checks windows updates*
Gah, 2 new ones to do.

I generally install them as soon as my system try pops up with that bubble thing. I've not had any noticeable probelms.

mairving — Wed, 23 Apr 2003 21:13:11 +0000

It is a big groan sometimes patching systems. I installed an Exchange patch the other day. After that the Exchange service wouldn't restart. So I uninstalled it, that didn't work. I reinstalled it and that didn't work. Finally after a couple of reboots and a couple of hours, I saw some documentation about moving the internal NIC to the top and the External to the bottom in the Bindings. Well it already was but when I brought the external to the top and then flipped it back to the bottom, rebooted the server and it was fixed. Still two needless hours of my time wasted.

Often I think MS rushes patches out without a whole bunch of testing just to fix a security hole. Then when they find out that they break things they issue another fix. It is a sad process.

There are about 30 meg's of Critical Updates since the first of the year. I haven't really had much problem with the patch that you listed. Is it on a server exposed to the wild or on a machine sitting behind a firewall.