The product group released the May 2017 Cumulative Update for the SharePoint 2013 product family.
For May 2017 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, May 2017 CU includes all fixes from May 2017 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).
This CU fixes the regression introduced in March 2017 CU and March 2017 PU (MS17-14) which prevents opening Word documents via Office Web Application Server if they are contained in sites with spaces in their names
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 May 2017 CU should be available at the following locations in a couple of hours:
- KB 3191911 – SharePoint Foundation 2013 May 2017 CU
- KB 3191913 – SharePoint Server 2013 May 2017 CU
- KB 3191912 – SharePoint Server 2013 with Project Server May 2017 CU
- KB 3191888 – Office Web Apps Server 2013 May 2017 CU – this is also a security update!
The Full Server Packages for May 2017 CU are available through the following links:
- Download SharePoint Foundation 2013 May 2017 CU
- Download SharePoint Server 2013 May 2017 CU
- Download Project Server 2013 May 2017 CU
- Download Office Web Apps Server 2013 May 2017 CU – this is also a security update!
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: May 2017 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
does anybody know whether the search bug in task lists (contained in Dec CU) is resolved with this SharePoint 2013 CU?
MS said a solution could not be expected before the May 2017 CU….
Thanks in advanced
if you mean the issue that inplace search stopped filterung items in tasks lists after December 2016 CU: yes that fix is included in this CU.
Perfect. Thanks. 🙂
My initial testing on this bug looks like it has been resolved. I can now filter on lists of type TasksWithTimelineAndHierarchy
Have not confirmed when this started. Believe it includes the Dec-May CUs.
Rich Text Editor on page edit. Paste, preview would be displayed. Now iframe embeds no longer work in browsers other then Internet Explorer?
E.g. Youtube embed
Oct 2016 CU: worked
April CU: Only IE
May CU: Only IE
we had installed project server 2013 – July 2016 CU without a pre-requisite of Project server 2013 SP1 and we want to deploy march-2017 CU which has the same pre-requisite of Project server 2013 SP1. Can you help me to understand how can installed CU without pre-requisite?
I checked patch status and products installed on the server but found SP1 is not installed, so I am wondering how did we installed July 2016 CU.
which exact fix did you install from July 2016 CU?
Thanks for your reply !
We installed this CU – https://support.microsoft.com/en-us/help/3115291/july-12,-2016,-cumulative-update-for-project-server-2013-kb3115291
and now planning to install this – https://support.microsoft.com/en-us/help/3172462/march-14-2017-cumulative-update-for-project-server-2013-kb3172462
We are not concerned about the fix but about the pre-requisite, both July-2016 & March-2017 have the same pre-requisite of Project server 2013 SP1 and I don’t see Sp1 installed on farm servers.
We installed July CU is that means CU contains binaries of SP1 ?
I have downloaded the fix and I can see that it does not install if SP1 is not installed.
So it seems you have SP1 installed.
To verify this please run the following script which will provide the patch baseline of your system:
I ran script now found the below info
DisplayName : Microsoft SharePoint Server 2013
DisplayVersion : 15.0.4569.1506
DisplayName : Microsoftr Project Server 2013
DisplayVersion : 15.0.4569.1506
this looks like older version
this is the version number of Project Server / SharePoint Server with SP1 slipstream.
So SP1 is installed as assumed.
I guess you used the SP1 slipstream version for the initial install.
Thank you very much for the confirmation!
However, i am not aware of SP1 spitstream will check on that.
After having installed May 2017 CU for SP 2013 we discovered a regression related to “Reusable content” features. If you have items structured in folders/sub folders you will not be able to select them anymore from the pop up box.
Any thoughts ?
if you need this investigated ensure to open a support case with Microsoft.
Thx Stefan, we are doing it 🙂