Support Desk Extra - Windows XP SP2:

Still a Bleeding Edge Solution

Fixes Galore

The list of fixes for Windows XP Service Pack 2 fills an entire web page,

http://support.microsoft.com/default.aspx?kbid=811113 . The problem is that with these fixes, Microsoft has turned on features that have been present in some form in Windows XP since the beginning, but have been previously disabled. Enabling these features closes ports used by programs and applications, including Microsoft applications. The result is that you will need to know what your program needs to create exceptions so the programs in the best case can still run. Therein lies the problem. You will need to be a savvy individual to be able to make these modifications so your programs will run after Windows XP Service Pack 2 is installed.

What Does It ‘Break’

Our concern is in knowing that programs like Microsoft SQL Server, Outlook, Network Shares and CAD software from Autodesk are known to either have issues or not to work at all after the installation of this patch. Based on the vast number of applications a particular customer could be running and the interaction of those applications once SP2 is installed, we find ourselves in a quandary. Security and updates are important to everyone in the global community, but if the patch breaks the software that runs your business, the solution could prove to be worse than the problem.

Release Software vs. Beta Software

I myself have been a beta tester for various software companies over the years, and I understand what the implications of using that beta software are. Many people have been testing the different beta releases of this service pack. Microsoft seems to want to get the product released, even though there have been many delays due to problems and compatibility issues. When there is a potential for so many things not working at the same time, whether you are dealing with a new application, operating system or patches,  IT best practices and common sense seem to dictate that this patch be treated as if it were a new release entirely. Here is the link to the published ‘short list’ as of August 17, 2004 of applications that are known to have problems with Windows XP SP2 http://support.microsoft.com/default.aspx?kbid=842242 .

Before You Deploy

Based on the changes present here, before you deploy Windows XP Service Pack 2, you should:

1)       Check with all your hardware vendors to see if their product will work in this environment.

2)       Check with all your software vendors to see if their product will work in this environment.

3)       If there are problems, you may need to upgrade either hardware, software or both.

4)       If the applications do not work with SP2, you will need to decide if installing it is a show stopper.

5)       Test it on a variety of configurations before deploying. A weekend update to SP2 followed by a Monday where no one can work would be a bad scenario.

6)       Disable automatic update so this patch does not get loaded before you are ready to deploy it.

The following link leads to the release notes for Windows XP Service Pack 2 and many other links for what to expect and what the published issues on Microsoft’s web site are so far. http://support.microsoft.com/default.aspx?kbid=835935&product=windowsxpsp2 . Greater than 50 software vendors have reported problems with their applications and this service pack

Have A Question Or Comment?

We always like to get your feedback. After all, helping you to understand the issue at hand or new technology will result in better decisions, better connectivity, increased productivity and ultimately better security for hardware and software environments! If you have questions or comments about this article, contact me (JohnBoline@hagerman.com).