Print | posted on Wednesday, May 28, 2008 4:24 PM
Updated May 1st 2009
UPDATE: Service Pack 2 for SharePoint 2007 is now available. I will be posting another article detailing post SP2 hotfixes shortly. This page will not be updated further. Please deploy Service Pack 2 as soon as possible!
This is a list of the post Service Pack 1 hotfix packages for SharePoint 2007, primarily for my own reference.
This is not a list of fixes, but rather the update packages themselves. You will find below the build numbers and any notes for each release. These are the build numbers which show up in SharePoint Central Administration on the Servers In Farm page.
The SP1 build number is 18.104.22.16819
You shouldn't deploy these willy nilly unless you are experiencing issues - it's best to wait for the regular "roll up" packages.
I strongly recommend you always install all critical Windows Updates. In particular ensure you are running the latest service packs of each version of the .NET Framework installed on your servers. This one is important when running a least privilege farm. Without .NET 2.0 SP1 you will require an additional fix to get the Search Usage Analysis pages within SSP Admin working.
I also strongly recommend you deploy the IIS6 946517 fix, which resolves the issue with two threads locking the Timer Service and filling your event logs up with 7076, 6398 and 6432s. This is also known as the "Timer Job Shocker" by the boys in Premier Field Engineering (who BTW kick ass).
I also strongly recommend you deploy the Excel Services Security Update if you are running MOSS Enterprise.
Recently the SharePoint teams have, along with the rest of Office, moved to a twice monthly release of cumulative updates. This is a good thing in principle, but it remains to be seen if this will ease the updates burden for MOSS. Time will tell. UPDATE – time has told and this provides a huge improvement to the patching cycles of MOSS environments.
I'm a platform hygiene kinda guy so I keep my farms up to date, but remember to factor this maintenance into your architecture design work, and the SLAs for production. Check out Todd Carter's excellent article on the Zero Downtime Patching Myth.