Windows XP SP2:  Just Say No (For Now)

I have received a lot of emails since the last newsletter came out. Some of them have been in praise of our move to ‘warn’ people about the problems that exist with many applications and Windows XP Service Pack 2. Still others have expressed concern that we would recommend people not installing a patch. As time has passed, we are still adopting the ‘Just Say No’ attitude for installation of Windows XP Service Pack 2, and here is why you should too.

Fixes Galore
The list of fixes for Windows XP Service Pack 2 still fills an entire web page and that page is getting bigger. You can view the current list of bug fixes and inclusions at the following URL
http://support.microsoft.com/default.aspx?kbid=811113 . The problem with these fixes, as stated earlier, is that Microsoft has turned on features that have been present in some form in Windows XP since the beginning, but have been previously disabled. Enabling this features closes ports used by programs and applications, including Microsoft applications. Yes, I know many of you know how to go in and change the availability of port ID’s and can make the applications programs work, but that is not the issue. The issue is that something has to be done to make applications that worked previously work again after the service pack installation, and many software manufacturers (Autodesk included) have not ‘signed on’ to this product being supported with their applications. Autodesk now says that AutoCAD 2005 and AutoCAD LT 2005 are supported (see TS86068 at Autodesk.com under support, but none of the verticals are supported (MDT, ADT, Inventor, etc.) and no previous releases are supported either.

What Does It ‘Break’
We know 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.. 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. Still, once the fixes have been released and once you have the software updates (if required) for your applications to run in this new environment, it should be installed.

Microsoft Offers Compatibility Guide
As a result of the concerns (and fears) of system administrators and IT managers that SP2 may also break homegrown applications, many companies have delayed launching the software in the companies. To get the deployments back on track and keep developers' blood pressure down, Microsoft is offering the application compatibility testing guide. The guide, which can be retrieved from Microsoft's Download Center, is designed to help administrators "test and mitigate application compatibility issues “ but at more than 100 pages, this is not light reading. To see more on this, you can read the article at the following ZDNet URL http://zdnet.com.com/2100-1104-5323378.html

Microsoft Extends Blocks
Microsoft has now extended the delay that corporate users can choose with Service Pack 2. Initially, there was an allowed delay of 120 days (from August 16, 2004). This delay was put in place to allow customers time to thoroughly test SP2 on corporate networks. Due to all of the compatibility issues, computers makers, software vendors and VAR’s were recommending a go-slow approach to deployment. IBM sent out a memo telling its employees not to install the update because of potential incompatibilities as did many other companies. As a result of this backlash, on Tuesday, September 7, 2004, Microsoft extended the temporary blocking period to 240 days, or about eight months, from August. 16, 2004. At the end of this period, the Automatic Update mechanism will download SP2 to all Windows XP machines, the company said. Hopefully by then all the problems will be solved. You can read more on this at the following ZDNet URL http://zdnet.com.com/2100-1104-5355050.html

Before You Deploy
Based on the changes present here, we are still recommending that before you deploy Windows XP Service Pack 2, you should:

1) Check with all your hardware vendors to see if there product will work in this environment.
2) Check with all your software vendors to see if there 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).

 

All product names / logos, company names / logos are copyrights of their respective holders. John Boline is an MCSE, CNE, USE and a member of the Network Professional Association. The content herein is often based on late-breaking events. Much of the material is based on information from sources that are believed to be reliable. Hagerman & Company, Inc. disclaims all warranties as to the ultimate accuracy or completeness of the information. Hagerman & Company, Inc. and its employees shall have no liability for errors, omissions or inadequacies in the information contained within this article or for any interpretations thereof. The recommendations, positions and best practice policies outlined herein represent Hagerman & Company, Inc. initial analysis and therefore are subject to change as further information which may have bearing on these positions is made available. The reader assumes sole responsibility for the selection of these materials to achieve its intended results. The opinions expressed herein are subject to change without notice. Entire contents © 2004 Hagerman & Company, Inc. All rights reserved. Reproduction of this publication in any form without prior written permission is forbidden.