SharePoint 2016 August CU Complete Information

In this article, we will list all the Issues, which are fix in this August 2018 CU. This Month MSFT released two versions of it, one includes the Fixes for LPs and others don’t include the Fix for LPs. Now it is irrelevant that what language pack you installed or what base language of the SharePoint. You just simply install both exe and it will take care of everything. Security updates also part of the packages.

In this article, we will list all the issues which are fixed in this August's 2018 CU. This month, MSFT released two versions of it, one includes the fixes for LPs and the other one doesn't. Now it is irrelevant which language pack you installed or the base language of SharePoint. You just simply install both the .exe files and it will take care of everything. Security updates are also part of the packages.

What’s included

This CU includes all the previous CUs since SharePoint 2016 RTM. This CU also includes the Feature Pack 1 & Feature Pack 2.

This public update delivers Feature Pack 2 for SharePoint Server 2016, which contains the following feature.

  • SharePoint Framework (SPFx)

The following features are part of Feature Pack 1.

  • Administrative Actions Logging
  • MinRole enhancements
  • SharePoint Custom Tiles
  • Hybrid Auditing (preview)
  • Hybrid Taxonomy (preview)
  • OneDrive API for SharePoint on-premises
  • OneDrive for Business modern experience (available to Software Assurance customers)

Note
This CU also has a security update, which means you do not need to apply security updates separately if you apply this CU.

Improvements, fixes and security updates

This CU brings SharePoint & Project Server fixes, improvement, and security updates; here is the list of fixes published by MSFT.

Project Server 2016

  1. When a SharePoint Server 2013 content database that contains Project Server sites is mounted on a SharePoint Server 2016 farm that was set up by using PowerShell cmdlets, Project Server-related database tables are not created. Therefore, the Project Server related sites cannot be opened.

  2. When you restore Enterprise custom fields by using the Administrative Backup and Administrative Restore features in SharePoint Server 2016 Central Administration, you experience a "ForeignKeyViolationError."

  3. If you set a long Duration or Work value for a task in a project and then try to achieve the value of the WorkTimeSpan property by using the Project Server 2016 client-side object model (CSOM), an overflow occurs in the WorkTimeSpan property. For example, when you set the Duration value to 75 days, the DurationTimeSpan property displays 36000. However, the WorkTimeSpan property displays -35791.3941333333.

  4. You receive an unknown error when you set a lookup table value for a local custom field through the Project Server 2016 client-side object model (CSOM).

  5. When you enter 1d in the Committed Work field for a resource engagement, the Committed Work field always displays the default 8h for 1 day instead of the project calendar setting from the Enterprise Global.

  6. This update makes the Task Type field and Task.IsEffortDriven property updatable through the Project Server 2016 client-side object model (CSOM).

  7. When you create an enterprise resource through Project Server 2016 client-side object model (CSOM), you are unable to set values for required custom fields. Therefore, you can’t create the enterprise resource.

SharePoint Server 2016

This update contains the following improvements and fixes for SharePoint Server 2016,

  1. When a web browser makes a cross-origin resource sharing (CORS) request to a SharePoint REST API, the browser typically sends an OPTIONS preflight request to SharePoint without authentication. SharePoint returns an HTTP 401 status code response for this preflight request, which is not correct.

    With this update, SharePoint introduces the option to respond to the CORS request by sending an HTTP 200 status code, which is the correct behavior. You must run the following commands in PowerShell to enable the new behavior,
    1. $stsConfig = Get-SPSecurityTokenServiceConfig  
    2. $stsConfig.ActivateOkResponseToCORSOptions = $true  
    3. $stsConfig.Update();  
  1. The Copy-SPSite command destroys the content type relationships in a document library. The content type settings in the document library of a new site collection are different from the settings of the source library. This issue occurs when you copy a site from the root (/) to an included URL (for example, /sites/copiedsite).

  2. You can’t search integer numbers from a Microsoft Excel workbook in SharePoint 2016. After you install this update, you can search integer numbers in Excel workbooks.

  3. This update adds better support for keyboard accessibility when you use the Item or Entity Picker dialog box of Business Connectivity Services by restoring the focus to the Browse button whenever the dialog box is closed.

  4. Assume that a SharePoint Server 2016 web application is using a Security Assertion Markup Language (SAML) Authentication Provider. When you request access to a site in the web application by an Active Directory Federation Services (ADFS) account, you get "Access Denied."

  5. The context menu of a document displays some options that the user doesn't have permissions to operate. Assume that you have only Read permission on the site, and you right-click a document in the library. The context menu of the document will display the Delete Item option. When you select the "..." column of the document, you may see Rename, Check Out, Workflows, and Shared With options.

  6. When a timesheet is deleted and then recreated, the actual work that's already been reported and approved doesn't reappear in the timesheet.

  7. A web application that has an auditing service hangs when the authentication type is changed on a separate web application.

  8. If there’s already a crawl running on a content source of a SharePoint Search service application when you trigger another crawl by using PowerShell on the same content source, you can’t stop the crawl on the content source through SharePoint or PowerShell. This update enables users to stop the crawl under such conditions.

Security Fix

  • This security update resolves vulnerabilities in Microsoft Office that could allow information disclosure if a user opens a specially crafted Office file.

Language-Dependent Fix

Translation improvements for Chinese.

Installation

As we know, this Month MSFT Release 2 CUs (one Include the LPs related fix and Other Non LP related fixes).

Prerequisite

  • To apply this update, you must have Microsoft SharePoint Server 2016 installed.

Restart information

  • If during the installation of the updates, certain components of SharePoint are running then it will ask you fto restart the server. So it depends upon your server.

Schema Change

  • This update updates the database schema so that the mean schema and Patch Version will change. You will see the same Patch number and Build Number.

Patch Number

  • 16.0.4732.1000
  • 16.0.4732.1001 (if LPs installed)

Known Issue with CU

No known issue with this CU.

Reference

See Also

Please check this Wiki for the SharePoint 2016 Build Numbers