> The .NET Framework is a "Recommended Update"... NOT a > "Critical Update". It has been my experience that you > should always pay attention to what you're installing.
I'm responding just because I really just want to strongly agree with this - especially when it comes to servers. The "Windows Update" stuff is a convenience to make the patch process easier, but it's still the user's/sysadmin's responsibility to make sure that updates are appropriate before installing them. > Critical updates are pretty straight forward... I usually > don't even review them. For your production servers, I'd recommend that you review EACH update, "critical" or not, to see if it's applicable to your configuration. To take that a step farther, in an ideal world, you wouldn't install any update to your production server before testing it on your staging server. I know that's not always possible, but it generally makes things work better. Ideally, you shouldn't even use "Windows Update" for production servers if you can find a better solution - if you have a bunch of servers, the last thing you want to do is have to patch each one by hand from the console. Instead, take a look at some of the patch solutions provided by Microsoft, such as setting up your own update server and downloading updates from the "Windows Update Catalog", or by third parties. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
