The product group released the Feature Pack 1 for the SharePoint Server 2016 product family.
Feature Pack 1 includes all fixes usually released as November 2016 CU but also several new features based on customer feedback, extending support for hybrid scenarios and developer needs, including:
- Administrative actions logging for common SharePoint administrative Actions in Central Administration and with Windows PowerShell..
- MinRole enhancements to support small and medium-sized farms.
- A OneDrive for Business modern experience.
- Custom tiles in the SharePoint app launcher.
- SharePoint hybrid auditing unified across site collections on-premises and in Office 365.
- Hybrid taxonomy unified across on-premises and Office 365.
- OneDrive API for SharePoint on-premises.
For more details on feature pack 1 please have a look at the official Feature Pack release blog post from Bill Baer.
The KB articles for Feature Pack 1 aka November 2016 CU are available at the following location:
- KB 3127940 – Update for SharePoint Server 2016 November 2016 (language independent)
- KB 3127942 – Update for SharePoint Server 2016 November 2016 (language dependent fixes)
- No fixes released for Office Online Server 2016 November 2016
The download for November 2016 CU is available through the following link:
- Download Update for SharePoint Server 2016 November 2016 (language independent)
- Download SharePoint Server 2016 November 2016 (language dependent fixes)
- No fixes released for Office Online Server 2016 November 2016
It is irrelevant which language you pick on the drop down in download center. Even the language dependent fixes are all in the same package for all languages.
After installing the fixes you need to run the SharePoint 2016 Products Configuration Wizard on each machine in the farm. If you prefer to run the command line version psconfig.exe ensure to have a look here for the correct options.
SharePoint 2016 November 2016 CU Build Numbers:
Language Independent fix: 16.0.4456.1002
Language Dependent fix: 16.0.4456.1002
To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.
You can use the SharePoint Server 2016 Patch Build Numbers Powershell Module to identify the patch level of all SharePoint components.
- 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: November 2016 Office Update Release
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SharePoint Server 2016 Patch Build Numbers Powershell Module
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified
- Blog: SharePoint does not have a build version. Full Stop.
- Blog: Feature Pack 1 for SharePoint Server 2016 now available.
Is the Volume License (VL) media version available already, or what is the best approach to install a brand new farm that would include the new Feature Pack? I’d like to install a min-role farm using the new hybrid roles.
to install a new farm I would suggest to install SP2016 RTM and November 2016 CU.
Then run PSConfig and create the farm.
KB3127940 has this fix: “If the web.config file size is larger than 250 KB which is the default file size limit, the SharePoint farm can’t be visited because IIS doesn’t load the web.config file.”
We’ve already hit this limit on our SharePoint 2013 farm. We had to change the web.config limit in the registry ([HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp\Configuration!MaxWebConfigFileSizeInKB]).
How does this update affect us after we migrate to 2016? Can we drop the registry change, keep the big web.config and expect it to work?
the fix just updates the same registry key you mentiond above with a value of 900 during the fix Installation.
Hi Stefan, I have just installed SharePoint 2016 November 2016 CU hoping that it could resolve an issue with custom actions and document sets, however the problem is still there. Here is a description of the issue https://techcommunity.microsoft.com/t5/SharePoint/Custom-actions-list-item-menu-not-shown-for-document-sets/m-p/31399/thread-id/2716 Do you know if this problem (possible bug because the issue does not happen on SP 2010/2013/Online) will be resolve in a future CU?
I have found a very similar problem description related to SharePoint online. A fix was released for SPO but it seems no customer requested a fix for SharePoint 2016.
Fixes are only created if requested by customers through a hotfix request.
I would recommend to open a support case with Microsoft to investigate if you are running into the same known issue and if yes to port the fix to SharePoint 2016.
I will follow your recommendation.
Any details of Office Online Server new patch release?
No patch for Office Online Server was released in November 2016.
October 2016 CU is the most current CU for OOS.
There was one – https://blogs.office.com/2016/11/18/office-online-server-november-release/
Also this blog post https://blogs.technet.microsoft.com/office_web_apps_server_2013_support_blog/2016/10/26/oos-unhealthy/ refers to this update – “The new version of Office Online Server released on 11/17/2016 has these health fixes in place.”
Are both KB3127940 and KB3127942 required to warranty the successful deployment of November 2016 CU?
yes – both fixes are required.
The download link for 3127942, SharePoint Server 2016 November 2016 (language dependent fixes) , is broken. Do you happen to know the new link?
I just tested the link and it works fine for me.
Now it works.
After I install the fix on all farm servers, I ran the production configuration wizard. the configuration failed. with following error:
An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:
Action 184.108.40.206 of Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence failed. (EventID:ajywk)
Exception: The object ‘MSP_SECURITY_RELATIONS_VIEW’ is dependent on column ‘ENCODED_CLAIM’. (EventID:ajywk)
What I have missed? Please help?
I haven’t seen this error and would recommend to open a support Case with Microsoft to get this analyzed.
Has anyone have any solution to this? I have this exact message too.
Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 220.127.116.11 of Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence failed. —> System.Data.SqlClient.SqlException: The object ‘MSP_SECURITY_RELATIONS_VIEW’ is dependent on column ‘ENCODED_CLAIM’.
I too am getting this same error… New conversion from SP 10->13->16. Works fine in the other environments, can not apply configuration wizard unless I unmount this particular database
It’d be great if you could provide a new “demystification” article, as you did on the 2013 platform.
I’m especially wondering whether I’ll be required to install a feature pack to get future security updates etc.
In other words, are CUs and FPs two different independent tracks?
– Is there a dependency on Feature Packs to have all previous cumulative updates?
– Is there a dependency on cumulative updates to have all previous feature packs installed?
a Feature pack is just a CU with additional Features.
Each later CU contains the Feature pack functionality as well.