Client setup is unable to download contents from a cloud distribution point in Configuration Manager current branch, version 2006

អនុវត្តចំពោះ៖ Microsoft Endpoint Configuration Manager (current branch – version 2006)

Symptoms


A client update is available to resolve the following issues with the Configuration Manager client setup program (ccmsetup.exe). 

1. When a cloud management gateway (CMG) is configured to use a cloud distribution point, ccmsetup.exe is unable to download the client installation file (ccmsetup.cab) from Azure blob storage. This leads to increased CMG traffic. It also delays installation or upgrade of the client because it will fall back to use another management point if available. Errors resembling the following are recorded in the ccmsetup.log on the client.

2. Internet-facing clients that only use PKI client certificates for authentication are unable to install or upgrade after installation of the following update rollup.

KB 4578605 Update Rollup for Microsoft Endpoint Configuration Manager version 2006

This occurs if the option Use PKI client certificate (client authentication capability) when available is disabled on the Communication Security tab of Site Properties. Errors resembling the following are recorded in the ccmsetup.log file on the client.

Update information for Microsoft Endpoint Configuration Manager, version 2006


This update is available in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using early update ring or globally available builds of version 2006, and have the following update rollup installed.

KB 4578605 Update Rollup for Microsoft Endpoint Configuration Manager version 2006

Restart information

This update does not require a computer restart but will initiate a site reset after installation.

Update replacement information

The client patch (.MSP file) contained in this update supercedes the versions that shipped with update rollup KB 4578605 and update KB 4575787. Therefore, only one client upgrade is required.

Additional installation 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')

If the value 1 is returned, the site is up to date, with all the hotfixes applied on its parent primary site.

If the value 0 is returned, the site has not installed all the fixes that are applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site.