The product group released the March 2018 Cumulative Update for the SharePoint 2013 product family.
For March 2018 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, March 2018 CU includes all fixes from March 2018 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 March 2018 CU should be available at the following locations in a couple of hours:
- KB 4018299 – SharePoint Foundation 2013 March 2018 CU
- KB 4018302 – SharePoint Server 2013 March 2018 CU
- KB 4018301 – Project Server 2013 March 2018 CU
- KB 4011692 – Office Web Apps Server 2013 in March 2018 CU – This is also a security update!
The Full Server Packages for March 2018 CU are available through the following links:
- Download SharePoint Foundation 2013 March 2018 CU
- Download SharePoint Server 2013 March 2018 CU
- Download Project Server 2013 March 2018 CU
- Download Office Web Apps Server 2013 March 2018 CU
Important: If your farm has been on a patch level lower than July 2015 CU ensure to read the following blog post:
Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation 2013 CU. And the Project Server 2013 CU also contains the SharePoint Server 2013 CU and SharePoint Foundation 2013 CU.
- Technet: Updated Product Servicing Policy for SharePoint 2013
- 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: March 2018 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
After March CU 2018 was installed, one box is reporting a missing component: August 8, 2017, cumulative update for Project Server 2013 (KB4011074). Get-SPProduct -Local doesn’t fix the problem. I had to remove that box from our Farm, because was stopping us to continue running PSConfig. 7 boxes got patched with no issues, but the one we removed, is reporting August 2017 CU missing (which was applied on whole farm a while back)
something is wrong with this box. The error indicates that the msp files for August 2017 CU are not installed on the affected machine. Get-SPProduct -local synchronizes the info about all installed msp files again into the database. If this does not solve the issue, then either the msp files are really not installed or the installer database on the box is broken.
I would recommend to verify again that the fixes are installed and if yes, open a support ticket with Microsoft.
I patched the SharePoint 2013 farm with March 2018 CU by downloading the package from official Microsoft download site
After the installation and PSConfig was successful when I go to Manage Servers in farm page or check the version through powershell it shows me
Configuration database version: 15.0.5009.1000
Whereas as per the MS article @ https://support.microsoft.com/en-us/help/4018302/march-13-2018-cumulative-update-for-sharepoint-enterprise-server-2013 it should have been 15.0.5015.1002
Please advise what could be the reason.
you are mixing different things. The configuration database version is not the version of the patch. See here for details: