SCCM current branch 1710 KB4086143

SCCM current branch 1710 KB4086143.

Improvements and issues that are fixed

• The 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.
  • 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. In environments that have TLS 1.2 enabled, you may experience the following errors.

• The Office 365 application wizard may terminate unexpectedly when importing a volume license SKU.  
• The AADDeviceID şi 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-premise 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.
• In a co-management scenario, a client on Configuration Manager current branch version 1710 is unable to switch the Endpoint Protection workload to Intune.  
• 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.