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

Summary

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

For more information about the changes that are included in version 1710, see the following:

• What's new in version 1710 of System Center Configuration Manager

• Summary of changes in System Center Configuration Manager current branch, version 1710

Improvements and issues that are fixed

• Asynchronous running of PowerShell scripts is improved for Configuration Manager clients. See Create and run PowerShell scripts from the Configuration Manager console for the latest details on this prerelease feature.

• In environments that have TLS 1.2 enabled, you may experience the following errors.

  • Errors resembling the following may be recorded in the ObjReplMgr.log file on the site server:

    +++Begin processing changed OPA objects
    *** [08001][18][Microsoft][ODBC SQL Server Driver][Shared Memory]SSL Security error
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.

  • When you perform a fresh installation from CD, errors resembling the following may be recorded in the ConfigMgrSetup.log file on the site server:

    *** [08001][18][Microsoft][ODBC SQL Server Driver][Shared Memory]SSL Security error
    *** [01000][1][Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (SECCreateCredentials()),
    *** Failed to connect to the SQL Server, connection type:<ServerFQDN> MASTER.

  For more information about TLS 1.2, refer to How to enable TLS 1.2 for Configuration Manager.

• The Office 365 application wizard may terminate unexpectedly when importing a volume license SKU.

   

• The AADDeviceID and AADTenantID properties of a device may be displayed incorrectly in the Configuration Manager console.

   

• Content downloading from a Cloud Distribution Point may fail when the client is using an Alternate Content Provider.

   

• The Create Application Wizard in the Configuration Manager console is updated to work with new URL formats in the Microsoft Store.

   

• After you install Update Rollup 1 for Configuration Manager 1710, the client push install method cannot be used to repair an existing client installation. Errors resembling the following are recorded in the ccm.log file:

  Mobile client on the target machine has a newer version. Not processing this CCR.

   

• After you upgrade to Configuration Manager current branch version 1710, customers are unable to enroll Samsung KNOX devices for mobile device management.

   

• The Configuration Manager client cannot be installed through the Cloud Management Gateway if the client was previously installed on the same device for on-premises management. An error resembling the following is recorded in the CMService.log file:

  Response - MessageID: {guid} ResponseHeader: HTTP/1.1 400 Failed to issue token~~...

  
  Note This entry is truncated for readability.

• Site replication delays may occur after HTTPS communication is enabled for a Management Point in an environment where a cloud management gateway is used.

   

• The Configuration Manager client forces a shutdown of Office 365 applications when updates are applied if the installation deadline has approached.

  After you install this update, the client will require a restart of the computer if Office 365 applications are running at the installation deadline.

• When you migrate content in environments that have several hundred distribution points or more, the data-collecting process may time out when it tries to discover the source distribution points. This occurs when you use the option to share distribution points between source and distribution hierarchies.

   

• After you upgrade to Configuration Manager current branch, version 1710, the client will not repair itself for corruption of its database files.

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.

Be aware that it also applies to 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. See Install in-console Updates for System Center Configuration Manager for detailed information.

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, with all the hotfixes applied on 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.

References

Learn about the terminology Microsoft uses to describe software updates.