SharePoint 2010 and February 2012 CU


The next cumulative update is available. It is still highly recommended to install SP1 before you install post SP1 updates.

KB articles are having sometimes a bit delay but the download of the fixes are possible.

MSF2010:
2597132 The full server package for Microsoft SharePoint Foundation 2010
http://support.microsoft.com/default.aspx?scid=kb;EN-US;2597132

Download link: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2597132&kbln=en-us

SPS2010:
2597150 The full server package for SharePoint Server 2010 and contains also the MSF2010 fixes so you need only this one package.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;2597150

Download link: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2597150&kbln=en-us

Important for all Server Applications listed above:
After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or “psconfig –cmd upgrade –inplace b2b -wait” in command line. This needs to be done on all servers in the farm with SharePoint installed. You can run psconfig in parallel on all SharePoint machines.

SP1 references:

My post for June CU and SP1:
http://blogs.msdn.com/b/joerg_sinemus/archive/2011/06/29/sharepoint-2010-sp1-and-post-sp1-june-2011-cu.aspx

Post made by my colleague regarding a rerelease of June CU:
http://blogs.technet.com/b/stefan_gossner/archive/2011/07/12/june-2011-cu-for-sharepoint-2010-has-been-re-released.aspx

Posts by CAPES:
SharePoint 2010 SP1 and the June Cumulative Update for SharePoint 2010

Office 2010 Service Pack 1 – 5 Common questions regarding the Service Pack

Comments (2)

  1. Thanks for letting us know! Cheers, C.

  2. Vince says:

    The ability to request and download the CU has been pulled from the KB due to an undisclosed "technical problem". Community advice is to NOT install this update if you have already downloaded it. Either wait for it to be re-released or install the Feb CU, which was re-released in March. This CU release and re-release pattern is getting disturbingly common and causing a lot of re-work. The June 2011 is another example – it was released, pulled, then re-released. It makes for good reason to go with MS' own recommendation NOT to install a CU unless it fixes a specific problem you are having. Even then, you better wait at least 2 months after CU release before applying a CU to a production system. Waiting will help ensure the CU has been thoroughly tested by the community and that it won't be pulled for re-release.