A new cumulative update for SharePoint Server 2016 has been released (May 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.5005.1000 (Language independent CU)
SharePoint 2016 CU – KB articles describing the CU:
- KB 4484336 – May 2020 Update for SharePoint Server 2016 (language independent)
- This CU does not include an update to language-dependent components for SharePoint Server 2016 (the most recent language-dependent component update is 4484301)
SharePoint Server 2016 CU – CU download link:
- Download May 2020 Update for SharePoint Server 2016 (language independent)
- This CU does not include an update to language-dependent components for SharePoint Server 2016 (the most recent language-dependent component update is 4484301)
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:
- language independent (updates language-independent components)
- 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 the following security advisories:
- Microsoft Common Vulnerabilities and Exposures CVE-2020-1023
- Microsoft Common Vulnerabilities and Exposures CVE-2020-1024
- Microsoft Common Vulnerabilities and Exposures CVE-2020-1069
- Microsoft Common Vulnerabilities and Exposures CVE-2020-1099
- Microsoft Common Vulnerabilities and Exposures CVE-2020-1100
- Microsoft Common Vulnerabilities and Exposures CVE-2020-1101
- Microsoft Common Vulnerabilities and Exposures CVE-2020-1102
- Microsoft Common Vulnerabilities and Exposures CVE-2020-1103
- Microsoft Common Vulnerabilities and Exposures CVE-2020-1104
- Microsoft Common Vulnerabilities and Exposures CVE-2020-1105
- Microsoft Common Vulnerabilities and Exposures CVE-2020-1106
- Microsoft Common Vulnerabilities and Exposures CVE-2020-1107
This security update contains improvements and fixes for the following nonsecurity issues in SharePoint Server 2016:
- Changes the “Scheduled Start Date” and “Scheduled End Date” fields in a publishing page to format the date field according to the correct locale.
- Updates SharePoint search crawler to send GET requests by using HTTP 1.1 if the HTTP 1.0 requests fail.
- Updates the Search word breaker to tag IP addresses and GUIDs as named entities for all languages except Korean.
- Fixes an issue in which axis values may be truncated when you use SharePoint Server 2016 to convert a file that contains charts to PDF.
- Fixes the HTTP 404 response error when you access site collections in newly created or mounted content databases.
- Consider the following scenario:
- You have a web application that uses Windows claims authentication only.
- You create an Active Directory (AD) user that has a mail account name that’s not the same as the user principal name (UPN), and the AD user doesn’t exist in the UserInfo list.
- You create a new team site and also create a custom list that has a “person” field.
- You use the Quick Edit mode to set the person field to the AD user.
In this scenario, the AD user isn’t validated.
Komentáře