Update 1 for System Center Configuration Manager version 1610, early wave

Applies to: System Center Configuration Manager (current branch - version 1610)

Summary


Administrators who opted in to the early wave deployment of System Center Configuration Manager current branch, version 1610, have an update available in the Updates and Servicing node of the Configuration Manager console. This update, made available on December 12, 2016, addresses important late-breaking issues that were discovered during the final release process for version 1610. This update does not apply to sites that update or install version 1610 after December 1, 2016.

Issues that are fixed

  • After you upgrade from Configuration Manager version 1606 to version 1610, Software Center does not open on client computers. This issue can occur if an application is deployed to the version 1606 client after the site was upgraded to version 1610. Additionally, you receive the following error message:
    Software Center cannot be loaded. There is a problem loading the required components for Software Center.

  • The SMS Agent Host process (ccmexec.exe) can use 100 percent of available CPU time. This issue occurs if the client is currently downloading content and loses connectivity to the Distribution Point. The Data Transfer Service component on the client continues to retry the connection quickly for features that can be retried (such as a time-out). This causes the increase in CPU usage until the Content Transfer Manager job times out.
  • Improved support for handling multiple range requests to the Background Intelligent Transfer Service (BITS) for Windows Express Update Files.
  • When you click the notification that is generated by Windows Hello for Business, the Configuration Manager Software Center is opened instead of the expected Hello for Business application.
  • The SMS Executive Service can end unexpectedly when the Cloud Management Gateway and Network Device Enrollment Service are collocated on the site server.
  • The data collecting process that is used to migrate from a site version earlier that Configuration Manager version 1606 fails when you query Boundary Group data. The Migmctrl.log file contains a System.Data.SqlClient.SqlException exception that references the BoundaryGroup table.
  • Manual or automated (scheduled) deletion of user discovery data fails on the Central Administration Site. This issue occurs because a read-only site table is referenced in the deletion trigger.
  • The Setup Windows and ConfigMgr task sequence does not install the Configuration Manager client on Windows 7 computers.
  • Task sequence deployments that have a great effect on the user may fail because of a missing policy. This issue occurs for task sequences that were created before the upgrade to Configuration Manager version 1610.
  • Task sequences that are configured by using the Access content directly from the distribution point option freeze when they try to download content.
  • After you upgrade to Configuration Manager version 1610, you receive the following error message when you try to deploy task sequences:
    The selected task sequence uses an invalid package or application reference. Use task sequence editor to correct the error or select a different task sequence.

    Note This error message occurs randomly for task sequences that reference other packages or applications.
  • The Updates and Servicing node is missing from the Configuration Manager console after you do a site recovery. This issue occurs when the Reinstall the site server and Use a site database that has been manually recovered options were selected in the recovery process.

Update information for System Center Configuration Manager, version 1610

This update is available for installation in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using early wave (Fast Ring) builds of version 1610 that were downloaded after November 17, 2016 and before December 1, 2016.

To confirm which early wave build is used, look for the Package GUID of C43A89E4-B642-4FC8-ABF0-255BF5D88D82 in the console. You can check this by adding the Package GUID column to the details pane of the Updates and Servicing node.

Restart information

You do not have to restart the computer after you apply this update.

Update replacement information

This update does not replace any previously released update.