Premium Content

Access "Patch deployment best practices: Rushing patches isn't always better"

Victor Garza, Contributor Published: 06 Dec 2012

Are you a procrastinator? If so, you have plenty of time to put off installing Service Pack 2 for Windows XP. In fact, consider this an opportunity to rethink patch deployment best practices altogether. But, this really isn't procrastinating; it's being prudent. Unless there's a worm slamming your perimeter, you shouldn't ever rush to deploy patches, hot fixes or service packs. SP2 is no exception, despite unquestionable security benefits: the default-on firewall, secure browsing and e-mail settings, and better malware resistance. This is no ordinary service pack installation; it's akin to a full upgrade. SP2 is massive--the enterprise version weighs in at more than 266 MB, and the home version is about 80 MB. Given its complexity and the inevitable application conflicts and snafus, most shops are waiting until they've completed their own testing or seen the snags hit by early adopters (see NewSCAN). As a colleague of mine said, "I never met a service pack that I wanted to blindly deploy." Let's face it: No one runs a pure OS-anything shop. Most networks are... Access >>>

Access TechTarget
Premium Content for Free.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

What's Inside

Features

More Premium Content Accessible For Free