In this article, we will list all the issues, which are fixed in this April's 2017 CU. This Month MSFT released two versions of it, one includes the Fixes for LPs and others don’t include the Fix for LPs. Now it is irrelevant what language pack you installed or what the base language of the SharePoint is. You just simply install both exes and it will take care of everything.
What’s Included
This CU includes all the previous CUs since SharePoint 2016 RTM. This CU also includes the Feature Pack 1.
The following features are part of Feature Pack 1.
- Administrative Actions Logging
- MinRole enhancements
- SharePoint Custom Tiles
- Hybrid Auditing (preview)
- Hybrid Taxonomy (preview)
- OneDrive API for SharePoint on-premises
- OneDrive for Business modern experience (available to Software Assurance customers)
Note
This CU also a security update, which means you do not need to apply security updates separately if you apply this CU.
Improvements and fixes
This CU brings a lot of SharePoint & Project Server fixes, here is the list of fixes published by MSFT.
Project Server 2016
- When you browse PWA pages that have HTML grids either in Internet Explorer standards or enterprise mode, you can't scroll pages because the scroll bars don't appear.
- Screen readers don't identify that the Delegate Name and the User Name fields on the Add Delegation page are required.
SharePoint Server 2016
This update contains the following improvements and fixes for SharePoint Server 2016:
- When you start a crawl for a web application that's migrated from SharePoint Server 2013, the crawl fails, and the content isn't searchable. This issue occurs because the connector retrieves the TenantId property for two times.
- A new SPServer.CompliantWithMinRole property is added so that farm administrators can see the MinRole compliance status of each server in the farm without using Central Administration. You can see the server compliance status in Windows PowerShell by running:
Get-SPServer | FT -Property Address, Role, CompliantWithMinRole
- Sometimes psconfig copies side-by-side files unnecessarily.
- Improves word breaking for Thai.
- Translates some terms in multiple languages to make sure that the meaning is accurate.
- When PSConfig runs its tasks, it first stops certain services on the local server, such as the SharePoint Timer service. If you click Cancel before the final task runs to the end, or if PSConfig encounters an unexpected exception, it won't automatically restart the services that it stopped.
- In an upgrade, the log file would record warnings about avoiding an attempt to change the database version because it recognizes that this can't be done. This log file message severity is now changed from warnings to information so that administrators don't think an invalid action was performed during an upgrade.
- Fix an issue about the compilation of search query completion dictionaries. Query suggestions timer job sometimes fails because of duplicate key constraint violation.
- If you have a SharePoint 2013 site that uses a Serbian language pack, the site fails to upgrade when you attach the content database to SharePoint Server 2016. This is fixed.
Note Certain features in an upgraded Serbian site may not function correctly. This will be fixed in a future update.
Language-Dependent Fix
- Translates some terms in multiple languages to make sure that the meaning is accurate.
Installation
As we know, this Month MSFT Release 2 CUs (one Include the LPs related fix and Other Non LP related fixes).
Prerequisite
- To apply this update, you must have Microsoft SharePoint Server 2016 installed.
Restart information
- If during the Installation of the Updates Certain Component of the SharePoint is running then it will ask you to Restart the server. So it depends upon your server.
Schema Change
- This update updates the database schema so that the mean schema and Patch Version will change. You will see the same Patch number and Build Number.
Patch Number
Known Issue with CU
This CU also fixes the longer time issue with Installation of packages.
Reference
See Also
Please check this Wiki for the SharePoint 2016 Build Numbers