Update for SharePoint Server 2016 (November 2019 CU)

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

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

SharePoint 2016 CU – KB articles describing the CU:

  • KB 4484143 – November 2019 Update for SharePoint Server 2016 (language independent)
  • KB 4484147 – November 2019 Update for SharePoint Server 2016 (language dependent)

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 information disclosure vulnerability that exists in Microsoft SharePoint if an attacker uploads a specially crafted file to the SharePoint Server. To learn more about the vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2019-1443.

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

  • This update corrects some regional settings display names.
  • Removes the Hybrid Auditing feature from SharePoint Server 2016.
  • Reduces the severity of certain upgrade sequence messages from WARNING to INFO. These messages indicate that the upgrade action doesn’t have to make any changes because its database extension is currently not enabled in the database. For example, you will no longer see upgrade messages such as the following be labeled as warnings:

    “Ignoring upgrade sequence: Microsoft.SharePoint.BusinessData.Upgrade.BdcDatabaseExtensionUpgradeSequence because related content database extension Microsoft.SharePoint.BusinessData.SharedService.BdcDatabaseExtension is not enabled.”

  • Fixes an issue that causes failures when you upload documents that contain links to very long URLs.
  • Fixes an issue in which the web part displays no content when users visit a Content Search Web Part (CSWP) from the Google’s page viewer or set the AlwaysRenderOnServer boolean in a Content Search Web Part (CSWP) to True.
  • Fixes an issue in which the Product Version Timer Job fails on dedicated Search and Distributed Cache servers.
  • Fixes an issue in which Publishing Cache items are missing page field data after the IIS app pool restarts.
  • When a web application uses Default Configuration to configure SAML-based claims authentication by using Active Directory Federation Services (AD FS) and the people picker account resolution, users from an external trusted domain experience the following issues:
    • They cannot log on to a site.
    • They cannot be resolved by People Picker if they are set up by using ADFS and have “Email” as the identity claim.

This security update contains a fix for the following nonsecurity issue in Project Server 2016:

  • In a Project Web App (PWA) project in which a proposed resource is replaced by a committed resource (or vice versa), existing assignments aren’t replaced by the new resource. Instead, the assignments are lost.

Komentáře