Update for SharePoint Server 2016 (March 2020 CU)

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

A new cumulative update for SharePoint Server 2016 has been released (March 2020 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.4978.1000 (Language independent CU)
16.0.4978.1000 (Language dependent CU)

SharePoint 2016 CU – KB articles describing the CU:

  • KB 4484272 – March 2020 Update for SharePoint Server 2016 (language independent)
  • KB 4484275 – March 2020 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 remote code execution vulnerability that exists in Microsoft Word software if the program does not correctly handle objects in memory. To learn more about the vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2020-0850 and Microsoft Common Vulnerabilities and Exposures CVE-2020-0892.

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 the following security advisories:

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

  • Adds support for the SameSite cookie attribute to remain compatible with changes in how web browsers such as Chrome handle cookies.
  • When a list view uses GroupBy on a calculated DateTime field and includes a multi-valued lookup field, users can’t expand any of the groups in the view. A “working on it” message appears where the group should be expanded, and an error dialog box appears. After this update is applied, the issue is fixed.
  • After you create an enterprise custom field, the keyboard focus doesn’t land on the next interactive element after you activate the Select value button.
  • After you import an updated thesaurus into the Search Service Application, you may see a “something went wrong” error message when you search from the Search box.
  • When you copy items that are declared as records through Windows Explorer, the copied items keep the record declaration status. This update fixes this issue.
  • When a user opens multiple SharePoint links on multiple browser tabs, enters credentials in one of the tabs, and then refreshes the other tabs, the sign-in process doesn’t occur seamlessly. Instead, the user is redirected to the root site and not actual site.
  • Site collection level mappings do not occur for Default.aspx in each site’s page library because the SiteId for Default.aspx is not generated correctly. After the fix is installed, the customized schema in site collection level will become active for default.aspx.

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

  • In Project Web App (PWA), you can’t edit in a lookup table’s Value and Description columns while you use the Chrome browser.
  • You edit a resource in Project Web App and use the Chrome browser. In this situation, although initials may exist for a work resource that’s tied to a Windows user account, the Initials field isn’t populated and appears blank. Therefore, if the resource is saved, the blank initials are saved over the correct initials.
  • You can’t navigate through the tables on the Approvals and Resource pages by using a keyboard.

 

Komentáře