Update for SharePoint Server 2016 (July 2019 CU)

25.7.2019    |    komentáře   komentářů: 0

A new cumulative update for SharePoint Server 2016 has been released (July 2019 CU).
This CU includes both Feature Pack 2, which has been included since the September CU (September 2017 CU), and the previous Feature Pack 1.

SP Build:
16.0.4873.1000 (Language independent CU)

SharePoint 2016 CU – KB articles describing the CU:

  • KB 4475520 – July 2019 Update for SharePoint Server 2016 (language independent)
  • This CU does not include an update to language-dependent components for SharePoint Server 2016 (the most recent language-dependent component update is 4461507)

SharePoint Server 2016 CU – CU download link:

After installation, remember to run the SharePoint 2016 Products Configuration Wizard (SharePoint 2016 Products Configuration Wizard), or the following command:
PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install

Notice

Feature Pack 2 also includes all functionality from Feature Pack 1.

Always install both packages in this order:

  1. language independent (updates language-independent components)
  2. language dependent (updates language-dependent components)

For language-dependent packages, it does not matter which language you select, as each package contains updates for all languages.

If you install a new language pack on your SharePoint Server 2016 farm, you must then reinstall the language-dependent update package.

Remember that Distributed Cache must also be updated alongside SharePoint; see How to update Distributed Cache correctly and for Office Online Server, you must have the current RTM release; see  How to update Office Online Server.

Included fixes and improvements

The fixes and improvements listed for this CU are excerpts from official Microsoft KB articles in their original language (EN).

SharePoint Server 2016

This security update resolves an Authentication Bypass vulnerability that allows SAML tokens to be signed by using arbitrary symmetric keys in Windows Communication Foundation (WCF) and Windows Identity Foundation (WIF). To learn more about the vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2019-1006 and Microsoft Common Vulnerabilities and Exposures CVE-2019-1134.

This update contains the following improvements in SharePoint Server 2016:

  • Adds support for the new Japanese era name to the Chinese word breaker to make sure that the name will be broken correctly.
  • Makes general improvements for notebooks that are located in folders that are synced through OneDrive.

Contains fixes for the following nonsecurity issues in SharePoint Server 2016:

  • You can‘t create a subsite based on a template that includes content in a site collection that has a retention policy.
  • Query Builder takes a long time to load or times out if there are many managed properties (for example, more than 10 thousand) in the Search service application (SSA).
  • Fixes an error when re-executing the backup and restore operations after executing the backup and restore operations with UI mode.
  • Fixes an issue in which resetting the role inheritance by using the SPWeb.ResetRoleInheritance method does not work on copied sites that are created by using the Copy-SPSite cmdlet.

  • In some cases, existing files are overwritten even if users don’t explicitly overwrite the files.

Project Server 2016

Contains the following improvements and fixes for nonsecurity issues in Project Server 2016:

  • Makes changes so that the first year of an era in Japanese dates on a timeline view shows as the special Kanji character (元). The Japanese date format is now consistent between the calendar date picker and the timeline view.
  • You can now update a task dependency lead and lag time by using the LinkLagDuration property through the client-side object model (CSOM). Similar to other duration properties (such as the Task.Duration property in the Task Object), LinkLagDuration accepts either a string or an integer value, such as “1d” or “480” to indicate one day of work.
  • After you change actual work values in a timesheet, you find that the columnar Total work values in the time-phased grid part of the view does not sum correctly.
  • When you query project-level information through the client-side object model (CSOM), read performance is slow if the Project Owner field is included.

Komentáře