Windows Server

Windows Server 2003 Service Pack 2 sneaks out the door


Even though Windows Vista just shipped, the next version of Windows Server remains somewhere over the horizon.  As such, that means continuing to support Windows Server 2003.  Microsoft has kept the OS going by first releasing Service Pack 1 and then by releasing Windows Server 2003 R2 which included SP1 plus a few other tweaks. 

Microsoft has been talking about releasing Service Pack 2 for Windows Server 2003 for a while now, but they only said that it would be available 'in Q1 2007'. With no formal announcement, imagine my surprise when I started up one of the test servers here today and fired up Windows Update:

 


 

 

Lo and behold, Windows Server 2003 SP2 was there waiting to be installed.  Checking Microsoft's Windows Server 2003 SP2 Web site revealed nothing but information about the Release Candidate, not the Service Pack itself. (By the time you're viewing this, it might have changed.)

So, being a test server, I decided to install it. It's funny how those Service Packs sneak up on you when you're not looking. 

12 comments
Mr.Newman
Mr.Newman

I've just looked at Microsoft Website and saw that SP2 fixes a lot of errors concerning .net and com+. The big list of errors, It seems that microsoft's programmer working only making mistakes and then fixing their own errors! LOL

rye_guy
rye_guy

This was called Zero Patch Tuesday, eh. So much for a relaxing month. And yes, what's in the SP?

croney1979
croney1979

How did the install go? What's new in this service pack?

nganslaw
nganslaw

I have deployed Win2003 SP2 on 4 Production servers, 6 in-house servers and I can tell you with confidence that there not only did it solve several problems in our environment, but after almost a month of testing, we have found 0 new problems.

706pbd
706pbd

is that XP Pro x64 is based on the code tree of Windows Server 2003 Windows NT5.2), not the code basis of WinXP Pro (Windows NT5.1). This explains why WinXP Pro x64 was never updated along with the x32 version- it's NOT actually related. So when W2KIII x64 received an update to SP2, so did the x64 "version" of WinXP. http://support.microsoft.com/kb/914962 "Note The x64-based versions of Windows Server 2003 and Microsoft Windows XP Professional x64 Edition are based on the Windows Server 2003 code tree. Service and support activities for Windows XP Professional x64 Edition use the Windows Server 2003 tree and do not use the Windows XP client tree. For more information about the x64-based versions of Windows Server 2003 and about Windows XP Professional x64 Edition, click the following article number to view the article in the Microsoft Knowledge Base: 888733 (http://support.microsoft.com/kb/888733/) A description of the x64-based versions of Windows Server 2003 and of Windows XP Professional x64 Edition" BTW, Vista (nee Longhorn) is technically NT6.0......

Dennis.A.Thalacker
Dennis.A.Thalacker

For the past two years I have installed all Microsoft Critical, Security and Software patches on 70+ production servers automatically usually within 3 days of release. Problems = 0

John Sheesley - TechRepublic Pro
John Sheesley - TechRepublic Pro

Oh yeah... most definitely in a production environment you'd want to test SP2 out before installing it. This is why Automatic Updates are often sometimes a bad idea. In some cases, the fixes just break something. I went ahead and installed it because this was running on a test server. If it blows up, nobody's cursing except for me... and a few editors who want to test things.

Why Me Worry?
Why Me Worry?

deploying onto production systems? I have learned time and time again from experience to be very careful with simply throwing new patches and service packs on production systems, especially those that come from Microsoft. I'd test this thing every which way imagineable to be sure it won't blow up my servers during critical production hours.

Editor's Picks