Update for SharePoint Server 2016 (January 2019 CU)

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

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

SharePoint 2016 CU – KB articles describing the CU:

  • KB 4461598 – January 2019 Update for SharePoint Server 2016 (language independent)
  • This CU does not include an update to language-dependent components 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 vulnerabilities in Microsoft Office that could allow remote code execution if a user opens a specially crafted Office file. To learn more about these vulnerabilities, see Microsoft Common Vulnerabilities and Exposures CVE-2019-0585,  Microsoft Common Vulnerabilities and Exposures CVE-2019-0557, Microsoft Common Vulnerabilities and Exposures CVE-2019-0558, and Microsoft Common Vulnerabilities and Exposures CVE-2019-0562.

This security update contains the following improvements in SharePoint Server 2016:

  • Improves Thai word breaking for more than 10 words.
  • Improves Turkish word breaking so that words can be correctly broken in some common cases where they previously were not.

This security update contains fixes for the following nonsecurity issues in SharePoint Server 2016:

  • When you use the REpresentational State Transfer (REST) API to query a specific project’s queue jobs, the queue jobs collection is not returned.
  • This update fixes the following issues that concern Quick Parts:
  • When you insert a SharePoint Library column as a Quick Part in a document that contains double-byte character sets (DBCS) characters in the file name, Word 2016 crashes.

  • If a SharePoint lookup field’s name contains a space or other special characters, the text for the field values is not displayed when you insert the information as a Quick Part in a Word document.

Project Server 2016

This security update contains fixes for the following nonsecurity issues in Project Server 2016:

  • If you update both a task’s name and Actual Cost value through the Client-Side Object Model (CSOM), the task name is lost. Additionally, other fields that were set during the same update are lost.
  • You can’t get all the details of a dependency link, such as the lag duration and project UID properties, through the Client-Side Object Model (CSOM).

  • Assume that you have selected PEN, AED, or other values in the Currency Settings section on the Additional Server Settings page. When you create a project from Project Web App (PWA), you experience a “ProjectOptCurrencySymbolInvalid” error, and the project is not successfully created.

Komentáře