Although Windows Server 2003 SP1 has fewer application compatibility issues than Windows XP SP2, Microsoft is providing a blocking toolkit to help organizations stop Automatic Update from installing SP1.

The use of the Automatic Update service is more prevalent with Windows XP than Windows Server, but some organizations do use this service to automatically download and install security updates and other updates to both Windows clients and servers. Because Windows Server 2003 SP1 contains new features and updates to existing features that could impact critical applications, some organizations might not be ready to install it when Microsoft makes it available via the Microsoft Update and Windows Update services on July 26, 2005.

The blocking toolkit contains a command-line executable, a script, and a Group Policy template. To prevent the automatic installation of SP1 on servers using Automatic Update, administrators can run the executable on a server, use the script to install the block on multiple servers, or use Group Policy to apply the template. The block, which sets a Registry key, persists until it is removed by running the tool or script with the correct parameter, removing the Group Policy. If the block is not removed by March 30, 2006 (the one-year anniversary of the SP1 release), it will automatically expire.

The Windows Server 2003 SP1 blocker toolkit can be downloaded from www.microsoft.com/downloads/details.aspx?FamilyId=FC145B0B-C148-445A-82BA-9B2F3AEF6E60.

Details of the changes in Windows Server 2003 SP1 are described in "Service Pack Enhances Windows Server Security" on page 10 of the Feb. 2005 Update.

For a chart summarizing the bug fixes in Windows Server 2003 SP1, see "What Windows Server 2003 SP1 Fixes" on page 9 of the May 2005 Update.