Update for SharePoint Server 2016 (April 2019 CU)

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

A new cumulative update for SharePoint Server 2016 has been released (April 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.4834.1000 (Language independent CU)
16.0.4834.1000 (Language dependent CU)

SharePoint 2016 CU – KB articles describing the CU:

  • KB 4464510 – April 2019 Update for SharePoint Server 2016 (language independent)
  • KB 4461507 – April 2019 Update for SharePoint Server 2016 (language dependent)
  • This CU does not include an update for Office Online Server 2016

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 a cross-site-scripting (XSS) vulnerability that exists when Microsoft SharePoint Server does not correctly sanitize a specially crafted web request to an affected SharePoint server. To learn more about the vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2019-0830 and Microsoft Common Vulnerabilities and Exposures CVE-2019-0831.

This update improves translations of a PowerShell warning message for multiple languages versions of SharePoint Server 2016.

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

  • When the Missing server side dependencies health analyzer rule runs on a server that’s not running the SPWebService service, an error message that states that some web parts are missing in the system is displayed in the health analysis report.
  • The filter functionality in an Asset Picker control doesn’t work and shows a deprecated style of UI.
  • Variations ignore the features that aren’t installed on a farm instead of blocking provisioning on a new site.

  • If you add a column that has spaces in its column title to a SharePoint list or document, the column title is displayed as having encoded characters. This issue occurs when the Multilingual User Interface (MUI) is enabled and the current language on your computer is different from the SharePoint site’s default language.

Project Server 2016

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

  • When you query many projects in batches through the client-side object model (CSOM), the project custom fields values are returned as “null.”
  • In an environment that uses the Japanese new era calendar, date formats that contain year aren’t applied on the Timeline view for dates after 1 May 2019.
  • When you query a project by using a Representational State Transfer (REST) call, not all of the expected project related properties are returned.
  • When you update a single resource through the client-side object model (CSOM), a Reporting (Resource Sync) job is unexpectedly invoked for all resources and the process takes much longer than expected.
  • If you directly publish a project without first doing an explicit save operation, you won’t receive an email notification for new or changed assignments.
  • Consider the following scenario:
    • You migrate your Project Server 2010 or 2013 data to Project Server 2016.
    • You open a project for editing from Project Web App.
    • You delete tasks in the project. You save the project.
  • In this situation, when the project is reopened, you may find that the tasks that were deleted previously reappear or that the project can’t be reopened.

Komentáře