Update for SharePoint Server 2016 (June 2021 CU)

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

A new cumulative update for SharePoint Server 2016 has been released (June 2021 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.5173.1000 (Language independent CU)
16.0.5173.1000 (Language dependent CU)

SharePoint 2016 CU – KB articles describing the CU:

  • KB 5001946 – June 2021 Update for SharePoint Server 2016 (language independent)
  • KB 5001922 – June 2021 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 a Microsoft SharePoint remote code execution vulnerability, SharePoint spoofing vulnerability, SharePoint Server information disclosure vulnerability, and SharePoint Server remote code execution vulnerability. To learn more about the vulnerabilities, see the following security advisories:

This security update resolves a Microsoft SharePoint Server remote code execution vulnerability. To learn more about the vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2021-31966.

This update contains security and reliability improvements.

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

  • Improves the performance of certain database operations that are done by the SharePoint Products Configuration Wizard (PSConfig), Timer service jobs, and other features.
  • Fixes an issue in which you receive the following error message when you try to clear a filter by using indexed columns in a SharePoint list that has many items:
    Cannot show the value of the filter. The field may not be filterable, or the number of items returned exceeds the list view threshold enforced by the administrator.
  • Fixes an issue in which Web Parts that depend on WPProperty don’t work correctly. To enable the Web Parts to work, you have to also follow the steps that are provided in KB 5003528 to declare the affected .NET types to be allowed to access WPProperty in the Web.config file.

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

  • On a task, you set the Status Manager.
  • You publish the project.
  • Later, while in the same editing session, you change the Status Manager settings.
  • You publish the project.

In this situation, the Status Manager property does not get updated in reporting. Instead of reflecting the new Status Manager, the old one is still observed.

Known issues in this update

  • DataFormWebPart may be blocked from accessing an external URL, and it generates “8scdc”event tags in SharePoint Unified Logging System (ULS) logs. For more information, see KB 5004210.
  • When third-party assemblies try to access some sensitive properties, user code might be blocked. When this issue occurs, “8gaol” event entries are logged in SharePoint Unified Logging System (ULS) logs. For example, you may find the following entry in ULS logs: 

    8gaol  Unable to access this sensitive property : <sensitive property name> from outer assembly. To fix this issue, install KB5002002 and follow the guidance in KB5004581 to enable trusted third-party assemblies.

Komentáře