Updates for SharePoint 2013 (August 2017 CU)

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

A new cumulative update has been released for SharePoint 2013 (August 2017 CU)
This CU fixes all SharePoint 2013 products.

SP Build: ​15.0.4953.1000

This CU is a full update (Uber package), requiring no earlier updates apart from SP1.

The CU includes all SharePoint 2013 security fixes released since SP1. It does not include SP1, which is required to install this CU.

Because of its size, the CU is split into separate CAB files and one executable. Download all these files into the same installation folder before starting the update.

SharePoint 2013 CU download files

SharePoint 2013 CU – KB articles describing the CU:

  • KB 4011073 – SharePoint Foundation 2013 August 2017 CU
  • KB 4011076 – SharePoint Server 2013 August 2017 CU
  • KB 4011074 – SharePoint Server 2013 with Project Server August 2017 CU
  • No Office Web Apps Server 2013 update was released with this CU

SharePoint 2013 CU – CU download link:

After installation, remember to run the SharePoint 2013 Products Configuration Wizard, or:
PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install

Important

Before installing the CU, ensure SP1 is already installed.

Installation may take up to five hours, so I recommend reading: Speeding up CU and SP installation on SharePoint 2013.

If your farm's patch level is earlier than July 2015 CU, run PSCONFIG immediately after installing the CU to update the schema of certain search databases. More at:
https://blogs.technet.microsoft.com/stefan_gossner/2015/07/15/important-psconfig-is-mandatory-for-july-2015-cu-for-sharepoint-2013

Always install only the CU matching your product version on a SharePoint 2013 farm.

The Project Server 2013 CU already includes:

  • CU SharePoint Server 2013
  • CU SharePoint Foundation 2013.

The SharePoint Server 2013 CU already includes:

  • CU SharePoint Foundation 2013

Remember to update Distributed Cache as well as SharePoint; see How to update Distributed Cache correctly.

Included fixes and improvements

This CU includes the following fixes and improvements.

SharePoint Foundation 2013

  • This update enables the hybrid content type for Black Forest tenants. More accurate user name mapper will be used in the hybrid content type migration.
  • This update adds a check box (Create Site Collections in SharePoint Online) in another self-service site creation page to enable hybrid self-service site creation.
  • This update improves the performance of the Variation List Propagation timer job after you update list items to a target source.
  • This update corrects a HTML heading structure issue in the Discussion Board views.
  • This update also fixes the following issues:
    • Deleted users are imported unexpectedly through a backup by using the SharePoint Content Migration APIs (previously known as the PRIME APIs), even if you have deleted the users from Active Directory.
    • The Name column in a Gantt view in a document library does not display the expected values.
    • Thestsadm setpropertycommand unexpectedly creates empty nodes under m_OleDbProviders. This causes intermittent high CPU.
    • Project view displays a failure in Edit mode if you enable the Custom Duration X setting in the Gantt Chart Format list.
    • The time for the iCal event is incorrect if you set the Time zone to Brasilia in the website’s Regional Setting.
    • When you edit a task and select Show More, the focus isn’t set on the first uncovered field as expected.
  • This update enables the hybrid content type for Black Forest tenants. More accurate user name mapper will be used in the hybrid content type migration.
  • Translates some terms in multiple languages to make sure that the meaning is accurate.
  • Translates the Open Menu link that JAWS uses to open the Edit Control Block (ECB) menu in a document library in multiple languages.

SharePoint Server 2013

  • This update enables the hybrid content type for Black Forest tenants. More accurate user name mapper will be used in the hybrid content type migration.
  • This update adds a checkbox (Create Site Collections in SharePoint Online) on another self-service site creation page to enable hybrid self-service site creation.
  • This update improves the translation accuracy for some terms in multiple languages versions of SharePoint Server 2013.
  • This update fixes the following issue:
    • Tenant users cannot crawl documents that contain invalid Unicode sequences by using hybrid search.

Project Server 2013

  • If you apply a filter that uses the Does not Contain filter test to a project that you are editing in Project Web App, tasks that have the filtered characters are still displayed.
  • Consider the following scenario:
    • You have a project-level custom field that’s defined.
    • A lookup table is associated with the custom field.
    • The lookup table allows multiple values to be selected.
    • You publish a project where multiple values are selected from the lookup table for the given custom field.

    In this situation, the report may show multiple copies of the same lookup table value.Consider the following scenario:

    • You have a local custom date field that’s defined by using a formula.
    • The formula rollup behavior is set to display either the minimum or maximum date value.
    • You edit a project in Project Web App and supply data into the fields that drive the formula in the local date field.

    In this situation, the date value does not roll up to related summary tasks.

  • When you try to rename a project that has a required project level custom field from Project Professional 2013, you may receive the following error message:

    Renaming project failed with error code hr = 0x80020009

  • When you try to rename a project to a name that contains the ampersand (&) character, you receive the following error message:

    Renaming project failed with error code hr = 0x80020009

Komentáře