Since July 2014 CU, the release cycle is now every month rather than the Bi-monthly cycle.
All Updates for SharePoint 2013 requires either the March 2013 PU OR SharePoint Server 2013 SP1 as mandatory baseline for all following CU’s !
You must install these updates on RTM Farms before you can install subsequent cumulative updates in the future!
For servers that include search components, you have to follow specific steps to ensure that you install the PU correctly.
Please find here important advise on how to do that:
How to install update packages on a SharePoint farm where search component and high availability search topologies are enabled
Please note the following change for new releases. Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Based on the file size, the SharePoint Server 2013 package has been now divided into several separate downloads. One contains the executable file (identified as i´.e. ubersrv2013kbxxxxxfullfilex64glb), while the other contains the .CAB file (identified as i.e. ubersrv1,…2 etc.). All of them are necessary and must be extracted to the same folder to successfully install the update. All of them are available by clicking the Download link in the KB article for the release.
As usual, you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm after installing the packages.
- The SharePoint Server pack (Uber) contains the Foundation packs, so you basically only need to install one Package.
- The Project Server Packs containing both, so if you install this one, no need for the other two to install additional
SharePoint 2013 Updates
Build Number: 15.0.4675.1000 (may vary due to individual components)
KB 2910945– SharePoint Foundation 2013 CU (Ubersts2013)
KB 2910938– SharePoint Server 2013 CU (Ubersrv2013)
KB 2910911– SharePoint Server 2013 with Project Server CU
KB 2899574 – Office Web Apps Server 2013 (Note: Office Web Apps Server 2013 fixes can be released in a different cadence to SharePoint)
There are several reports that people having problems with emails getting stuck in the Drop folder. This seems already happens since November CU.
You may find errors similar to this one:
"The Incoming E-Mail service has completed a batch. The elapsed time was 00:00:00.0155941. The service processed 2 message(s) in total.
Errors occurred processing 2 message(s):"
The issue is known by Product group and they're working on a fix being pushed out soon. If you have the described problem, please open a Microsoft Support case for it to get the fix as soon as possible.
Current known workaround:
remove storage sites quota and/or increase "Sandboxed Solutions Resource Quota".
- How to: install update packages on a SharePoint 2013 farm where search component and high availability search topologies are enabled
- Update center for Office, Office servers, and related products
- Software updates overview for SharePoint 2013
- Project 2013 and Project Server 2013: Language Packs
- CHANGE: SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging
- SharePoint Server 2013 July CU
- SharePoint Server 2013 SP1
All previous Updates:
- Build Matrix for SharePoint Server 2013
- Build Matrix for SharePoint Server 2010
- Build Matrix for SharePoint Server 2007 (aka MOSS)
3 thoughts on “December 2014 CU for SharePoint 2013”
Following my tradition in presenting a summarized "Build Numbers Cube Sheet" as I did so before
There seems to be an issue with incoming email after patching Dec 2014.
See in comments.
thnx for the notice, I have updated the "Know issue" section above.