Update for SharePoint Server 2016 (November 2018 CU)

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

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

SharePoint 2016 CU – KB articles describing the CU:

  • KB 4461501 – November 2018 Update for SharePoint Server 2016 (language independent)
  • This CU does not include an update to language-dependent components for SharePoint Server 2016 (language dependent)
  • 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 contains improvements and fixes for the following nonsecurity issues for SharePoint Server 2016:

Project Server 2016

This security update contains improvements and fixes for the following nonsecurity issues for Project Server 2016:
  • When multiple user and group synchronization jobs run in parallel, SQL deadlocks may occur. This issue may cause orphaned records in the MSP_WEB_SECURITY_PSMODE_PERMISSION_SYNC_STATES table that may also cause poor synchronization performance and large amounts of disk space consumed by the orphaned rows.
  • When an automatic approval rule is used to process status updates, for a given task, the Process Status field on the Tasks page is not changed from “Manager updated” to “Completed” even though the task is completed.
  • This update enables the ScheduledFromStart property to be set in the DraftProject class in the Client-Side Object Model (CSOM). You can now specify at creation of a new project whether it should be scheduled from the start date or the finish date.
  • This update adds the GraphicalIndicator property to the CustomField class in the Client-Side Object Model (CSOM). You can now set and get a Graphical Indicator for a custom field.
  • Approving status updates leads to an internal failure. The Info column in the Status updates history says that there was an internal error, and the Status says “Pending.” This problem can occur when a team member adds notes to their task status.
  • This update adds a UseForMatching property to the CustomField class in the Client-Side Object Model (CSOM). Through this property, you can set whether a field is used for matching generic resources.
  • Assume that you change the Week starts on setting for a project and save the project as a template in Project 2016. Then, you associate the template to an Enterprise Project Type (EPT) in Project Web App. When you create a new project from the Project Center by using the EPT, you find that the Week starts on setting doesn’t match the setting in the template.
  • Approving status updates leads to an internal failure. The Info column in the Status updates history says that there was an internal error, and the Status says “Pending.” This problem may occur when an internal services timeout occurs even though the Project Calculation Service RequestTimeLimits is set to an appropriate value.
  • In the Capacity Planning report, the Resource Center, Resource Assignments and Resource requests buttons on the Ribbon are not working.
  • This update adds the Departments property for the EnterpriseProjectType class in the Client-Side Object Model (CSOM). You can now set and get the department for an Enterprise Project Type.
  • The Current Max. Units (%) value of a resource that’s shown in Project Web App doesn’t match the current Max. Units value that’s seen in Project 2016.
  • A project’s or task’s calendar can’t be set through the Client-Side Object Model (CSOM). Instead, you see the error message: “Column “TASK_CAL_UID’ is read only.”

Komentáře