Post
Ask Question

SharePoint 2016 June 2017 CU

In this article, we will list all the issues that are fixed in June's 2017 CU. 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 what language pack you installed or what the base language of the SharePoint is. You just simply install both exes and it will take care of everything.

What’s Included

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

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 and fixes

This CU brings SharePoint & Project Server fixes, here is the list of fixes published by MSFT.

Project Server 2016

  1. Improve the performance of the Reporting (Project Publish) queue jobs.
  2. Consider the following scenario:
     
    1. A project manager publishes a task to a team member.
    2. The team member in either a timesheet or in tasks within Project Web App reports work that's earlier than what was scheduled. For example, 8 hours of work was scheduled on Wednesday but 8 hours of actual work was reported and submitted for Monday.
    3. The status manager approves the update.
    4. The team member zeros out the actual work and moves it to a later date.
    5. The status manager approves the update.
    6. The project is opened in Microsoft Project Server.

In this situation, the task's actual start date still reflects the earlier update instead of the new update where the actual start date is later.

  1. The Reporting (Project Publish) job takes longer than expected in Project Server 2016.
  2. Suppose you go to the Project Center page in the Project Web app and select many projects. When you click the Open In Microsoft Project option, nothing seems to happen, and the expected master project isn't created in Project Professional. Now, when you've selected more projects that can be used to create a master project via this method, you'll see a message that resembles the following:

Your selection exceeds the limit for the number of projects we can open at a time from Project Web App. We created a master project with the supported number of projects. You can then add additional projects by going through Insert Subproject.

  1. Resources from approved engagements become local resources in Project Professional if the project manager doesn't have sufficient permissions to that resource.
  2. When you add new tasks to a project while editing a project in PWA, formulas that use the Now() or CurrentDate() functions calculate incorrect results.
  3. An assignment's Finish Date, Work, and Remaining Work values are wrong when team members enter material units in PWA Tasks or Timesheets views.
  4. User-generated (ad hoc) custom filters that are applied to PWA views don't display data values. For example, you open a custom filter dialog box in Project Center to add a filter on a date column. After you save, close, and then reopen the dialog box, the date you set isn't displayed.
  5. When you submit a status update, task-level baseline data disappears from the Tasks view for the given task assignments.

SharePoint Server 2016

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

  1. The SPFile.Author property now has a value for installations after migrating from the classic-mode authentication to claims-based mode authentication.
  2. SPWebApplication FileNotFoundPage is not displayed correctly in some web browsers.
  3. Server-side defined timesheet view grouping doesn't work with custom fields.
  4. After you delete a search center subsite, you can't download search reports from site settings.
  5. When there are more than 100 site collections, you can see paging on the Tenant Admin page (TA_SiteCollections.aspx).
  6. Metadata navigation does not work for task lists.
  7. Word documents and PowerPoint presentations that have invalid hyperlinks aren't searchable.
  8. The body property of large files is dropped in Content Enrichment Web Service (CEWS). This update deletes the thresholds of the maximum body size of a document before sending it to CEWS.

Administrators who wish to suppress modern authentication with Office 2016 applications can now configure the SPSecurityTokenServiceConfig object when the SuppressModernAuthForOfficeClients property is set to $false.

  1. Office 2016 clients can’t authenticate with ADFS against SharePoint Server 2016. 

    Currently, Office 2016 clients and SharePoint Server 2016 use the Modern Authentication protocol to communicate. In certain scenarios, Modern Authentication isn’t supported by the Office 2016 clients, such as with ADFS installations. We’ve made improvements so that SharePoint administrators can now configure SharePoint to suppress Modern Authentication in Office 2016 clients in the June 2017 PU, final version.

    To configure SharePoint Server 2016 to suppress Modern Authentication in Office 2016 clients, run the following Windows PowerShell syntax in SharePoint 2016 Management Shell,
    • Before you can use the Add-SPShellAdmin cmdlet to grant permissions for users to run SharePoint Server 2016 cmdlets, verify that you meet all the following minimum requirements,

      • You must have membership in the security admin fixed server role on the SQL Server instance.
      • You must have membership in the db_owner fixed database role on all databases that are to be updated.
      • You must be a member of the Administrators group on the server on which you are running the Windows PowerShell cmdlet.

    • At the Windows PowerShell command prompt, type the following commands,

      Add-pssnapin Microsoft.sharepoint.powershell.dll
      $sts = get-SPSecurityTokenServiceConfig
      $sts.SuppressModernAuthForOfficeClients = $true
      $sts.Update()

    • Type iisreset /restart to restart IIS.
    • Type Net stop sptimerv4, and then type Net start sptimerv4 to restart the SPTimerService.
    • In Windows PowerShell, run the following command to verify that the change persisted,

      Note
      If you have closed the previous Windows PowerShell session then you must run the following command as shown. If you are in the same session, then you do not have to run the "Add-pssnapin Microsoft.sharepoint.powershell.dll" command again.
Add-pssnapin Microsoft.sharepoint.powershell.dll
$sts = get-SPSecurityTokenServiceConfig
$sts.SuppressModernAuthForOfficeClients

Note

Office 2013 clients are also affected. Microsoft is researching this problem and will post more information in this article when the information becomes available.

Language-Dependent Fix

  1. Improves the translation of Project Server 2016 in multiple languages.
  2. Translates some terms into multiple languages to make sure that the meaning is accurate.

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 Component of the SharePoint is running then it will ask you for the Restart the server. So its depend 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.4549.1001 or 16.0.4549.1000

Known Issue with CU

This CU also fixes the longer time issue with Installation of packages.

Reference

See Also

Please check this Wiki for the SharePoint 2016 Build Numbers


Similar Articles