Dwight Silverman of the Houston Chronicle has an excellent Windows XP SP2 guide. His conclusion: “Although downloading and installing an upgrade of the magnitude of Windows XP SP2 is not trivial, it’s worth it. The result will be improved peace of mind, and using the Net may actually be a pleasure again.”
The usual suspects are out with scare stories on SP2 breaking things. The Inquirer, for instance, has this scary headline: Teething troubles hit Windows XP SP2. “A number of people are having problems after they’ve installed service pack 2 of Windows XP.” Gee, imagine that. The details are, not so remarkably, lacking. “A number”? Care to be more specific?
IT World has a whole package of stories that pooh-pooh the upgrade, including this one: ITworld.com – Users report SP2 breaks their applications.
Because of the extensive changes that Service Pack 2 includes, the software giant has urged developers and IT professionals to test the update thoroughly. However, “it just seems that Microsoft doesn’t quite understand how difficult this is to do,” said Bill Lewkowski, CIO at Metropolitan Health, a company with 1,300 users recently migrated to Windows XP with SP1. “We can’t do unplanned, unbudgeted service pack releases that are very similar to putting in a whole new version of an operating system,” said Lewkowski. “I’m frustrated with Microsoft.”
Yeah, that darn Microsoft. They just don’t know how to test software. Poor Bill must have missed the gazillion or so stories announcing the public beta test of SP2, which has been available for public download and testing for months. Most corporations with 1000-plus users could easily qualify for special testing privileges, and those that are truly forward thinking have been doing so. The rest are busy whining to reporters about the released product.
The Seattle Post-Intelligencer has nice round-up of other reviews on its excellent Microsoft Blog.
Bottom line: If you’re a home user, get SP2. You’ll thank me. I assume you’re smart enough to do regular backups and that I don’t need to remind you about that. If you’re running a corporate network, you obviously want to do your own testing first, and you don’t want your users randomly installing operating system upgrades. If you aren’t prepared for this, you need to talk with your IT staff.