• December 2014 CU for SharePoint 2010 has been released

    Posted 1 month ago
    by Stefan Goßner}

    The product group released the December 2014 Cumulative Update for the SharePoint 2010 product family.

    For December 2014 CU we again have full server packages (also known as Uber packages). No other CU is required to fully patch SharePoint.

    Be aware that the December Cumulative Update for SharePoint 2010 is a Post-SP2 hotfix. It is required to have SP2 installed before installing the December CU.

    This CU includes all SharePoint 2010 fixes released since SP2. The CU does not include SP2.

    Attention: this CU no longer supports SP1! It is required to have SP2 installed for the base product and all installed language packs to install December 2014 CU for SharePoint 2010.

    The KB articles for December CU will be available at the following locations in a couple of days:

    • KB 2899585 - SharePoint Foundation 2010
    • KB 2899583 - SharePoint Server 2010
    • KB 2899587 - Project Server 2010

    The Full Server Packages for December 2014 CU are available through the following links:

    After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.

    Be aware that the SharePoint Server 2010 CU contains the SharePoint Foundation CU.
    That means only one package has to be installed for the SharePoint 2010 product family.

    Related Links:

  • December 2014 CU for SharePoint 2013 has been released

    Posted 1 month ago
    by Stefan Goßner}

    The product group released the December 2014 Cumulative Update for the SharePoint 2013 product family.

    For December 2014 CU we have full server packages (also known as Uber packages). No other CU is required to fully patch SharePoint.

    ATTENTION:

    Be aware that all Updates for SharePoint 2013 require SharePoint Server 2013 SP1 OR March 2013 PU for SharePoint 2013 to be installed first.

    Please also have a look at the article that discusses how to properly patch a SharePoint 2013 farm which has Search enabled (see below).

    Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hotfix Download Available link in the KB article for the release.

    This CU includes all SharePoint 2013 fixes released since RTM. The CU does not include SP1. You can install SP1 before or after installing this CU.

    The KB articles for December CU will be available at the following locations in a couple of days:

    • KB 2910945 - SharePoint Foundation 2013 December 2014 CU
    • KB 2910938 - SharePoint Server 2013 December 2014 CU
    • KB 2910911 - SharePoint Server 2013 with Project Server December 2014 CU
    • KB 2899574 - Office Web Apps Server 2013 December 2014 CU

    The Full Server Packages for December 2014 CU are available through the following links:

    After installing the fixes you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.

    Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation CU. And the SharePoint Server 2013 with Project Server CU contains Project Server CU, SharePoint Server CU and SharePoint Foundation CU.
     

    Related Info:

  • November 2014 CU for SharePoint 2010 has been released

    Posted 2 months ago
    by Stefan Goßner}

    The product group released the November 2014 Cumulative Update for the SharePoint 2010 product family.

    For November 2014 CU we again have full server packages (also known as Uber packages). Unlike August 2014 CU no other CU is required to fully patch SharePoint.

    Be aware that the November Cumulative Update for SharePoint 2010 is a Post-SP2 hotfix. It is required to have SP2 installed before installing the November CU.

    This CU includes all SharePoint 2010 fixes released since SP2. The CU does not include SP2.

    Attention: this is the first CU which no longer supports SP1! It is required to have SP2 installed for the base product and all installed language packs to install this November 2014 CU for SharePoint 2010.

    The KB articles for November CU will be available at the following locations in a couple of days:

    • KB 2889933 - SharePoint Foundation 2010
    • KB 2899478 - SharePoint Server 2010
    • KB 2899479 - Project Server 2010

    The Full Server Packages for November 2014 CU are available through the following links:

    After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.

    Be aware that the SharePoint Server 2010 CU contains the SharePoint Foundation CU.
    That means only one package has to be installed for the SharePoint 2010 product family.

    Related Links:

  • November 2014 CU for SharePoint 2013 has been released

    Posted 2 months ago
    by Stefan Goßner}

    [Update 2014-11-13] All the incorrect files have been removed now and the missing files in the project server CU has been uploaded as well.

    The product group released the November 2014 Cumulative Update for the SharePoint 2013 product family.

    For November 2014 CU we again have full server packages (also known as Uber packages). Unlike August 2014 CU no other CU is required to fully patch SharePoint.

    ATTENTION:

    Be aware that all Updates for SharePoint 2013 require SharePoint Server 2013 SP1 OR March 2013 PU for SharePoint 2013 to be installed first.

    Please also have a look at the article that discusses how to properly patch a SharePoint 2013 farm which has Search enabled (see below).

    Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hotfix Download Available link in the KB article for the release.

    This CU includes all SharePoint 2013 fixes released since RTM. The CU does not include SP1. You can install SP1 before or after installing this CU.

    The KB articles for November CU will be available at the following locations in a couple of days:

    • KB 2899468 - SharePoint Foundation 2013 November 2014 CU
    • KB 2889944 - SharePoint Server 2013 November 2014 CU
    • KB 2889949 - SharePoint Server 2013 with Project Server November 2014 CU
    • No Office Web Apps Server 2013 CU released this month

    The Full Server Packages for November 2014 CU are available through the following links:

    After installing the fixes you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.

    Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation CU. And the SharePoint Server 2013 with Project Server CU contains Project Server CU, SharePoint Server CU and SharePoint Foundation CU.
     

    Related Info:

  • Common question: why does the version number on the "Servers in Farm" page not change after installing October CU?

    Posted 3 months ago
    by Stefan Goßner}

    I received this question several times in the last couple of days via email, post comments and support cases - so I decided to answer it here for your benefit.

    I tried to answer this question in my SharePoint patching demystified article but it seems it is still not clear.

    This is the page I'm talking about:

    As shown on the screenshot the version number is the Configuration database version - it is not a "farm patch level". Something like a farm patch level does not exist as SharePoint patching is pretty complex and actually means to patch various different components.

    The answer why the above listed version number did not change is simple: The configuration database schema is not changed in October CU. Neither in SharePoint 2010, nor in SharePoint 2013. For SharePoint 2010 that can easily be explained: The only component directly accessing the configuration database is the SharePoint foundation component - which is more or less the database access layer for SharePoint Server. In October 2014 CU for SharePoint 2010 we did not release any patches for SharePoint Foundation - so the configuration database version cannot change.

    But what about SharePoint 2013? Here we actually ship a SharePoint foundation fix in October 2014 CU for SharePoint 2013. That is correct, but looking into the details of the patch listed here for SharePoint Foundation 2013 shows that the included fixes only address issues in localizable components (e.g. javascript and css files). So again - no components which influence the Configuration Database Schema version.

    What is the learning from this? Don't use the Configuration database version number to verify the patch level of your farm.

    More details here: SharePoint patching demystified