As the Windows XP Service Pack 2 upgrade rapidly approaches–unlike it’s upgrade cousin, Longhorn–companies are forced to evaluate whether they are ready to undergo the compatibility headaches that Microsoft is knowingly and willingly imposing on them. IBM, on the other hand, is not interested in playing that game.

Check out this InfoWorld article:
IBM tells employees not to install Windows XP update.

Unlike most OS service packs, XP SP2 is being treated like a major OS rev. It almost is, since it is the only OS revision Windows will see until Longhorn finally grows up. However, that very interim-like nature of the service pack begs the question, “Should companies upgrade to XP SP2, or should they save themselves the headache until Longhorn arrives?” This is a good question.

For software developers, the question is irrelevant. You must upgrade your testing and development boxes and make your software compatible with XP SP2 so that all who do upgrade will continue to use your software. Many probably are already in the process of doing this with beta or release candidate versions of XP SP2.

Where the question is really pertinent is regarding non-IT personnel and their computers. How soon do you deploy XP SP2 on all of their computers? As a programmer, I know that I will want to run compatibility tests on all of my applications in XP SP2 before I will be comfortable with our personnel upgrading. This will involve hours of testing and bug fixing. Thanks, Microsoft.

Then a realization sends a sinking feeling into your stomach: Doing nothing could potentially be more disastrous than recklessly deciding to upgrade without compatibility testing your software! Eventually Microsoft will release XP SP2 via Windows Update, where employees will be free to download and upgrade themselves. If you have mission-critical software that will break in XP SP2, this easy accessibility will result in catastrophe.

Fortunately, as the InfoWorld article points out, Microsoft will help companies in such a situation by providing them instructions to disable Windows Update from installing XP SP2. Nevertheless, it is a regrettable dilemma that Microsoft forces action to be taken to avoid catastrophe. And applying registry settings to all company computers to disable Windows Update from installing XP SP2 (which is the solution Microsoft is providing) may not be as easy as it sounds for some companies. If your company has hundreds or thousands of computers and you have no automated method in place for applying these settings across all of those computers, you could have a serious problem. These are precisely the scenarios that nurture disdain for Microsoft.

So when XP SP2 arrives, will your company nix it? Or will you upgrade? I am a strong believer in staying current, even if it means added expense. Especially in this case, the deplorable condition of XP’s security makes upgrading necessary. But I promise you we will be applying those registry settings to delay the installation of XP SP2, just like IBM. Sorry Microsoft, we just don’t have time for disaster today.