The product group released the April 2012 Cumulative Update for the SharePoint 2007 and 2010 product family.
The April Cumulative Update for SharePoint 2010 is a Post-SP1 hotfix. That means that you should ensure that SP1 is installed before the April CU.
The April Cumulative Update for SharePoint 2007 is a Post-SP3 hotfix. That means that you should ensure that SP3 is installed before the April CU.
The KB articles for April CU can be found at the following locations (they should be available in a couple of days):
- KB 2598130 – WSS 3.0
- KB 2598129 – MOSS 2007
- KB 2598321 – SharePoint Foundation 2010
- KB 2598151 – SharePoint Server 2010
- KB 2598152 – SharePoint Server 2010 with Project Server
As you see there is a separate Full Server Package for SharePoint Server 2010 with Project Server which simplifies patching of this common installation.
The Full Server Packages for April 2012 CU are available through the following links:
- Download WSS 3.0 April 2012 CU
- Download MOSS 2007 April 2012 CU
- Download SharePoint Foundation 2010 April 2012 CU
- Download SharePoint Server 2010 April 2012 CU
- Download SharePoint Server 2010 with Project Server April 2012 CU
After installing the fixes you need to run the SharePoint Products Configuration Wizard on each machine in the farm.
Be aware that the SharePoint Server 2010 CU contains the SharePoint Foundation CU. And the SharePoint Server 2010 with Project Server CU contains Project Server CU, SharePoint Server CU and SharePoint Foundation CU.
That means only one package has to be installed for the SharePoint 2010 product family.
If you need other April 2012 fixes from the Office 2007 and Office 2010 product family have a look at these KB articles:
Related Update Centers:
Permalink
Why does MS post these downloads without the proper associated KB articles to tell all the good admins what the heck the KB fixes? No one in their right mind would ever install these without proper details on the fixes included.
Permalink
In the KB articles listed above you will find a section "Issues that this hotfix package fixes" which includes links to the information you are looking for.
Permalink
Yes but they should be listed in an easy to find, and a readable format that can be search…hey why not use a SharePoint list?
Permalink
I have to say it is slightly annoying that with these CUs and hotfixes we have to submit a request and get e-mailed the link. It would be nice if at the very least they just had the link to the d/l for the executable in the KB articles.
Permalink
Stefan – any comments as to why this CU has been removed from MS Download? Links above state "This hotfix has been removed, due to technical issues". it would be interesting to learn why, and how you "revert" if you have alredey deployed this CU.
Permalink
Hi Henrik,
a problem has been identified in the April CU package which is currently being investigated.
Cheers,
Stefan
Permalink
Hi all,
April CU is now available again. The identified issues have been fixed.
Cheers,
Stefan
Permalink
Hi Stefan, I have already the older version of April 2012 CU installed, which causes "E-mail cannot be delivered because site is over quota or locked for editing" error, if quotas are not set. Can I fix this problem by intalling this newer version?
Permalink
Hi Markus,
the updated April CU can be installed on top of the original one. But the problem you described is not a known issue in April CU.
If installing the updated version does not help and you need assistance to resolve it you should open a support case with Microsoft.
Cheers,
Stefan
Permalink
hi Stefan, me too
thanks for sharing
June 2012 theme for sharepoint 2010 has been released. You can view detail: sharepoint2010template.com
Permalink
Stefan,
I'm upgrading my environments and for each I end up running into the SPAdmin timer job not able to start in the farm. I end up having to run two registry entries to fix. I found that Option #4 of the below link fixes the issue and allows the Admin service to run.
blogs.technet.com/…/kb934525-troubleshooting.aspx
Ideas?
Permalink
Hi David,
if Option #4 fixes the issue indicates that at least some databases in the farm did not upgrade the database schema. The force option might be the reason that it fixed the problem.
Cheers,
Stefan