NOTE! 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!
Starting with the July 2014 CU, the release cycle is now every month rather than the Bi-monthly cycle.
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.
Further Information: As usual, you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm after installing the packages.
Build Number: 15.0.4631.1001
KB 2882999 - SharePoint Foundation 2013 CU
KB 2882989 - SharePoint Server 2013 CU (aka Uber package)
KB 2883003 - Office Web Apps Server 2013 (Note: Office Web Apps Server 2013 fixes will be released in different cadence to SharePoint in future)
KB 2882990 – SharePoint Server 2013 with Project Server June 2014 CU (might be delayed)
All previous Updates:
After applying the July 2014 CU, we can no longer provision a new site collection from a custom site template. This is only if the custom site template was originally created at the root level of a site collection. However, if the site template was originally
created from a subsite, then it is able to be provisioned properly. Is this a known issue? Are there any fixes in-place yet?
Hi and sorry for delayed reply: This is not known as a regression yet. Maybe caused by something else?
We have recently published sept. CU (http://blogs.technet.com/b/stefan_gossner/archive/2014/09/10/september-2014-cu-for-sharepoint-2013-has-been-released.aspx).
The known regressions from july/August Cu are fixed with this one so maybe a chance to solve yours too, if it was caused by July CU.