The product group released the December 2015 Cumulative Update for the SharePoint 2010 product family.
For December 2015 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, December 2015 CU includes all SharePoint security fixes released with December 2015 PU.
Be aware that CU is a Post-SP2 hotfix. It is required to have SP2 installed before installing the CU.
It is required to have SP2 installed for the base product and all installed language packs to install December 2015 CU for SharePoint 2010.
This CU includes all SharePoint 2010 fixes (including all SharePoint 2010 security fixes) released since SP2. The CU does not include SP2.
The KB articles for December CU should be available at the following locations in a couple of hours:
- KB 3114418 – SharePoint Foundation 2010
- KB 3114408 – SharePoint Server 2010
- KB 3114405 – Project Server 2010
The Full Server Packages for December 2015 CU are already available through the following links:
- Download SharePoint Foundation 2010 December 2015 CU
- Download SharePoint Server 2010 December 2015 CU
- Download Project Server 2010 December 2015 CU
After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.
Be aware that the SharePoint Server 2010 CU contains the SharePoint Foundation CU.
That means only one package has to be installed for the SharePoint 2010 product family.
Related Links:
- SP2 for SharePoint 2010
- Common Question: What is the difference between a PU, a CU and a COD?
- SharePoint Patching demystified
- Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- December 2015 Office Update Release
- Update Center for Microsoft Office, Office Servers, and Related Products
- Updates for SharePoint Server 2010 and SharePoint Foundation 2010
- Updates for Project Server 2010
- Updates for Enterprise Search Products
Permalink
With SharePoint 2010 out of mainstream support since October, how much longer are CUs and other fixes going to be provided?
Permalink
Hi Demetris,
security fixes for SharePoint 2010 will be provided till end of extended support – so roughly another 5 years.
Regarding non-security fixes: there is still a backlog of hotfix requests which were requested and accepted before end of mainstream support. Till this backlog is processes there will be CUs but the number of non-security fixes in these CUs will get smaller and smaller from month to month.
Cheers,
Stefan
Permalink
After installing this CU (KB3114408 for SP2010) the version number displaced in Central Admin is 14.0.7162.5000, when it should be 14.0.7164.5000, it’s indicating Number CU.
This has happened on two of out test environments, just wondering if there is a bug in the CU?
Permalink
Hi Zahed,
your assumption is wrong. In December CU the database schema version has not changed so the version number will be the same as in November CU.
See here for details:
https://blogs.technet.microsoft.com/stefan_gossner/2014/10/23/common-question-why-does-the-version-number-on-the-servers-in-farm-page-not-change-after-installing-october-cu/
Cheers,
Stefan
Permalink
Hi Stefan.
I have a clean install of SharePoint 2010 with slipstreamed SP2. When I try to install this CU I get the error:
The expected version of the product was not found on the system
Any ideas?
Permalink
Hi Danny,
do you have any language packs installed? Might be that SP2 for one of the language packs is missing on your system.
You can run the following powershell script to check the patch baseline:
http://blogs.technet.com/b/stefan_gossner/archive/2015/04/20/powershell-script-to-display-version-info-for-sharepoint-product-and-language-packs.aspx
Cheers,
Stefan
Permalink
Hi Stefan,
It was indeed the version of a language pack that was causing the problem. It was installed but wasn’t applied. After running PSconfig again it works.
Permalink
I installed this CU and started psconfig in the cmd. But I ve only seen 10% finished for ages. No Error. I only found this in my Log.
05/04/2016 08:39:09 15 INF Entering function StringResourceManager.GetResourceString
05/04/2016 08:39:09 15 INF Resource id to be retrieved is UpgradeTimerJobStatus for language German (Germany)
05/04/2016 08:39:09 15 INF Resource retrieved id UpgradeTimerJobStatus is Im Prozess des Timerdiensts wird ein Upgrade der Farm ausgeführt. Der Task ist zu {0:F2} % abgeschlossen.
05/04/2016 08:39:09 15 INF Leaving function StringResourceManager.GetResourceString
05/04/2016 08:39:09 15 INF Entering function TaskBase.OnTaskNotify
05/04/2016 08:39:09 15 INF Creating the OnTaskNotify event for task upgrade
05/04/2016 08:39:09 15 INF Entering function TaskBase.FireTaskNotify
05/04/2016 08:39:09 15 INF Firing the OnTaskNotify event for task upgrade
05/04/2016 08:39:09 15 INF Entering function PsconfigBaseForm.TaskNotifyEventHandler
05/04/2016 08:39:09 15 INF Invoking the UI thread with the task notification event
05/04/2016 08:39:09 1 INF Entering function ConfigurationProgressForm.InvokeTaskNotifyEventHandler
05/04/2016 08:39:09 1 INF A NotifyEventArgs event received in TaskNotifyEventHandler. Task: upgrade NotifyEventArgs.EventCriticalityType: Im Prozess des Timerdiensts wird ein Upgrade der Farm ausgeführt. Der Task ist zu 10,00 % abgeschlossen. Message: info
05/04/2016 08:39:09 1 INF Acquiring the reader lock to retrieve the state
05/04/2016 08:39:09 1 INF Releasing the reader lock to retrieve the state
05/04/2016 08:39:09 1 INF Acquiring the reader lock to retrieve the state
05/04/2016 08:39:09 1 INF Releasing the reader lock to retrieve the state
05/04/2016 08:39:09 1 INF Updating the task notification additional message label
05/04/2016 08:39:09 1 INF Leaving function ConfigurationProgressForm.InvokeTaskNotifyEventHandler
05/04/2016 08:39:09 15 INF Sleeping an extra 1 ms so things don’t go too fast for the user for this task
05/04/2016 08:39:09 15 INF Leaving function PsconfigBaseForm.TaskNotifyEventHandler
05/04/2016 08:39:09 15 INF Leaving function TaskBase.FireTaskNotify
05/04/2016 08:39:09 15 INF Leaving function TaskBase.OnTaskNotify
05/04/2016 08:39:09 15 INF SyncUpgradeTimerJob: sleeping for 10 seconds
Permalink
Hi Mathias,
I would recommend to open a support case with Microsoft to analyze this problem in more detail.
Cheers,
Stefan