Update for SharePoint Server 2016 (July 2018 CU)

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

A new cumulative update for SharePoint Server 2016 has been released (July 2018 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: independent CU: 16.0.4717.1000

SharePoint 2016 CU – KB articles describing the CU:

  • KB 4022228 – July 2018 Update for SharePoint Server 2016 (language independent)
  • This CU does not include a language-dependent update for SharePoint Server 2016 (language dependent fixes)
  • 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

This CU includes the following fixes and improvements.

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-2018-8323, Microsoft Common Vulnerabilities and Exposures CVE-2018-8299, and Microsoft Common Vulnerabilities and Exposures CVE-2018-8300.

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

  • You can now add a site column that’s based on an external list to a custom list.
  • You experience an error when you use the External Content type-based site column. In this situation, you cannot add a site column that is based on an external list to a list. After you install this update, you must remove the site column,  and then add the site column again.
  • The SuppressModernAuthForOfficeClients property does not work for Outlook calendar synchronization. In this situation, the calendar does not synchronize with SharePoint Server. This issue occurs because SharePoint Server issues a modern authentication to on-premises Outlook clients. After you install this update, SharePoint Server will no longer issue a modern authentication to the clients.
  • A user whose name contains a comma cannot be resolved in the Quick Edit menu in SharePoint Server 2016.
  • A farm administrator whose name contains a period can’t upgrade SharePoint Apps.

  • When a farm administrator creates a search service application by using PowerShell, the database owner of the search service application database is the farm administrator and not the farm account that is used to run the timer service. The database owner of all databases should be the farm account. This update changes the owner of search-related databases to be the farm account.

Project Server 2016

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

  • The ReadResourcePlan API is now available even if the Resource Engagements feature is enabled.
  • It takes a long time to process tasks in a project through the client-side object model (CSOM) APIs in Project 2016.
  • Local custom date type fields that have a formula and have the calculation for the task and group summary rows option set to minimum or maximum are not rolled up correctly to summary tasks when you update a project in Project Web App.
  • It takes a long time to load entities such as tasks, resources, and assignments through the client-side object model (CSOM) APIs if custom fields exist.
  • When you use the Chrome browser to open a project from the Project Center where the project name includes spaces, you see the following error message:

    Project Web App was unable to find the specified Project.

    Additionally, this is followed by the following error message:

    Sorry, we were unable to open your project. Please try again. If this happens again, contact your administrator.

Komentáře