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
- 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.
- 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."
- 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.
- 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).
- 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.
- This update makes the Task Type field and Task.IsEffortDriven property updatable through the Project Server 2016 client-side object model (CSOM).
- 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,
- 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,- $stsConfig = Get-SPSecurityTokenServiceConfig
- $stsConfig.ActivateOkResponseToCORSOptions = $true
- $stsConfig.Update();

Hadshana KamalanathanPosted Sep 7, 2018, 12:01 PM
Thanks for sharing.....