Update rollup for System Center Configuration Manager current branch, version 1710

Applies to: System Center Configuration Manager 1710

Summary


This article describes the issues that are fixed in this update rollup for Microsoft System Center Configuration Manager current branch, version 1710.

Issues that are fixed


  • Clients who use Azure Active Directory (Azure AD) for authentication do not successfully communicate with a management point. This issue occurs if the management point is remote from the site server and configured by using a user account for SQL communication. 

     

  • The fallback time that is configured for content is not honored if distribution points or their content are inaccessible. In this situation, clients fall back faster than the time that is specified. 

     

  • Retrying a large single-file download, such as an Office 365 update file, may fail on a site server that has either of the following errors logged in the Patchdownload.log file: 

     

  • The Office 365 Application Installation Wizard may try to download content from an incorrect channel. This causes download failures. 

     

  • The Persist content in the client cache setting on Package Properties is not honored by clients. This causes the removal of the package contents when the client cache is cleared through the Configuration Manager Control Panel item. 

     

  • The Client Notification Restart request is processed incorrectly by remote management points. This causes a .bld notification file to be left in the \MP\Outboxes\bgb.box folder on the remote management point. 

     

  • Decommission-related State messages from co-managed client computers are processed incorrectly. Errors that resemble the following are logged in the Statesys.log file: 

     

  • State messages sent by Azure AD users may not be processed. This causes errors that resemble the following to be recorded in the Statesys.log file: 

     

  • Configuration Manager current branch, version 1710 clients are not upgraded on systems that are running Windows Server 2008 SP2. The client Setup program, Ccmsetup.exe, terminates unexpectedly, and an error that resembles the following is logged in the Application log: 

     

  • If a Configuration Manager client restarts during the process of retrying a task sequence policy download, that task sequence does not run automatically after the restart. The task sequence can be manually retried after the restart. 

     

  • Conditional access policies may block access to Office 365 applications for domain-joined devices after migrating to Intune standalone. 

     

  • Download of express updates may fail on Windows 10 clients because of an issue that affects files in temporary and cache folders. In this situation, errors that resemble the following are logged in the DeltaDownload.log file: 

     

  • The Configuration Manager console may terminate unexpectedly after you browse to a content location in the Office 365 Client Installation wizard. 

Update information for System Center Configuration Manager, version 1710


This update is available for installation in the Updates and Servicing node of the Configuration Manager console. It also applies to customers that are running Configuration Manager version 1710, first wave.

If the service connection point is in offline mode, you must reimport the update so that it is listed in the Configuration Manager console. For more information, see the Install in-console Updates for System Center Configuration Manager topic on the Microsoft Docs website.

After you install this update on a primary site, pre-existing secondary sites must be manually updated. To update a secondary site in the Configuration Manager console, click Administration, click Site Configuration, click Sites, click Recover Secondary Site, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files. Configurations and settings for the secondary site are not affected by this reinstallation. The new, upgraded, and reinstalled secondary sites under that primary site automatically receive this update.

Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:

select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')


Notes

  • If a value of 1 is returned, the site is up-to-date and has all the hotfixes applied to its parent primary site.
  • If a value of 0 is returned, the site has not installed all the fixes that were applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site.

File information


The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

References


Learn about the terminology Microsoft uses to describe software updates.