Update for SharePoint Server 2016 (September 2018 CU)

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

A new cumulative update for SharePoint Server 2016 has been released (September 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:
16.0.4744.1000 (Language independent CU)

SharePoint 2016 CU – KB articles describing the CU:

  • KB 4092459 – September 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

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 Microsoft Common Vulnerabilities and Exposures CVE-2018-8426, Microsoft Common Vulnerabilities and Exposures CVE-2018-8428, and Microsoft Common Vulnerabilities and Exposures CVE-2018-8431.

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

  • When you upload a document to a folder in a document library by using the Microsoft Edge browser, you can’t select a destination folder.
  • Assume that you set Managed Navigation for a subsite. When you navigate to a page on the subsite through the friendly URL of its term, the query variable {Page} or {Page.URL} returns an invalid URL for the page.
  • If a document is followed by a user, and its name contains special characters, you can’t open the document.
  • This update addresses some issues about the SharePoint Properties Panel in Word 2016. For example, when a document is renamed or a document has required properties, you receive the following error message: No SharePoint properties found.
  • This update also addresses the encoding issue of the document URL.
  • When you right-click an Analytic Chart or Grid in a PerformancePoint dashboard page, and then you select Filter > Top 10, you may receive the following error message: An unexpected error occurred.
  • This update increases the maximum length of URLs to 4,000 characters for reporting databases.

Project Server 2016

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

  • You can’t update the Status Manager field for a task through the Client-Side Object Model (CSOM).
  • When you create and insert a new task into a collapsed task outline in a project through the Client-Side Object Model (CSOM), the new task may be inserted at the wrong location in the project.
  • When you assign a resource to a task through the Client-Side Object Model (CSOM), this is done based on the resource name instead of pairing the resource and task GUID fields. As a result, the resource that is assigned to the task is not the one that is specified through CSOM.
  • When the scheduled Backup and Restore Timer job runs, SQL Server deadlocks occur when an archived version of the project has to be deleted before a new version can be written.
  • If a task link is created between two tasks, the dependency type of the task link can’t be changed through the Client-Side Object Model (CSOM).
  • The Task IsLockedByManager property can’t be set through the Client-Side Object Model (CSOM).
  • You can’t get the department that is associated with a custom field through the Client-Side Object Model (CSOM).
  • When you try to get an enterprise resource through the Client-Side Object Model (CSOM), the RES_ID property (the Unique ID of an enterprise resource), isn’t returned in the same manner as it is through the Project Server Interface (PSI).
  • You can’t return a list of template projects by using the Client-Side Object Model (CSOM) ProjectCollection.
  • You can’t update a Lookup Table mask through the Client-Side Object Model (CSOM). Therefore, you can’t programmatically add a value to the Lookup Table at the level that is not defined in the mask.

Komentáře