The product group released the September 2016 Cumulative Update for the SharePoint 2013 product family.
For September 2016 CU we have full server packages (also known as Uber packages). No other CU is required to fully patch SharePoint.
As this is a common question: Yes, September 2016 CU includes all fixes from September 2016 PU.
Be aware that all Updates for SharePoint 2013 require SharePoint Server 2013 SP1 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 (including all SharePoint 2013 security fixes) released since SP1. The CU does not include SP1. You need to install SP1 before installing this CU.
The KB articles for September 2016 CU should be available at the following locations in a couple of hours:
- KB 3118271 – SharePoint Foundation 2013 September 2016 CU
- KB 3118279 – SharePoint Server 2013 September 2016 CU
- KB 3118274 – SharePoint Server 2013 with Project Server September 2016 CU
- KB 3118270 – Office Web Apps Server 2013 September 2016 CU – this is also a security fix!
The Full Server Packages for September 2016 CU are available through the following links:
- Download SharePoint Foundation 2013 September 2016 CU
- Download SharePoint Server 2013 September 2016 CU
- Download Project Server 2013 September 2016 CU
- Download Office Web Apps Server 2013 September 2016 CU
Important: If your farm has been on a patch level lower than July 2015 CU: July 2015 CU and later contains a breaking change compared to earlier builds which requires running the SharePoint 2013 Products Configuration Wizard on each machine in the farm right after installing the CU.
If you don’t run PSCONFIG after installing this CU (on a farm which had a lower patch level than July 2015 CU) crawl might no longer work – so ensure to schedule a maintenance window when installing this CU which includes PSCONFIG runs.
See here for detail: https://blogs.technet.microsoft.com/stefan_gossner/2015/07/15/important-psconfig-is-mandatory-for-july-2015-cu-for-sharepoint-2013/
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.
- Blog: Common Question: What is the difference between a PU, a CU and a COD?
- Blog: SharePoint Patching demystified
- Blog: Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Blog: Support for SharePoint 2013 RTM has ended
- Blog: SP1 for SharePoint 2013
- Blog: September 2016 Office Update Release
- Technet: CHANGE: SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging
- Technet: Install a software update for SharePoint 2013
- Blog: How to: install update packages on a SharePoint 2013 farm where search component and high availability search topologies are enabled
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SQL Server 2014 and SharePoint Server 2013
I told my wife you were a “Senior Escalation Engineer” and she now thinks you are an elevator operator 🙂
That’s a good one! 🙂
we experience a strange issue with the Author refiner in the search results. When we are using the textbox in the refinement panel no results are displayed. When we click above on the name of the Author it is working. The problem is also described here: https://social.technet.microsoft.com/Forums/office/en-US/293f8176-1f25-4be1-a295-558568537f1a/author-search-refiner?forum=sharepointsearch
Is this a known bug? We have this problem on several SharePoint Farms (installed minimum September 2016 CU).
Thanks for your help
I double checked and this is not (yet) a known issue.
Please open a support case to get this analyzed.
We are planning to deploy September 2016 CU along with MS 16-133 Security update in our SP2013 farm. As Sept CU have MS16-107 bundled in it, wanted to know if we deploy Sept 2016 CU along with MS16-133 separately will there be any issues?. Because we will be installing MS16-133 along with Sept 2016 CU now, will there be any issue in terms of version mismatch if we plan to deploy Nov 2016 CU or Dec 2016 CU after 3 months as I see Nov 2016 CU has MS16-133 in it. Only reason we are deploying Sept 2016 CU is due to our company policies to deploy the patch.
the approach is supported and should not cause any issues but be aware that Microsoft is not able to test all combinations of CU patch levels with all combinations of security updates.
As always please ensure to evaluate this combination in your test environment to verify that it does not cause any side effects for your specific Setup.
Hi Stefan – so looks like no issues reported with Sept 2016 CU yet?
We’ve a need to install minimum July 2016 CU for SharePoint 2013 and I’m trying to track reported issues in the below thread. Your blog posts are very handy in this regard.
Appreciate any feedback you may have. Thank you!
Hi, i had after the installation of the september cu 2016 an issue with the “edit profile” functionality. Cause was the following error at the uls > Cannot open database “xxxx_Search” requested by the login. The login failed. Login failed for user ‘xxx\mysite’ (MySite App Pool Account). After granting sp-shelladmin for this user at the xxxx_Search the “edit profile” functionality start to work.