FIX: Content can't be downloaded from Cloud-Based Distribution Points in System Center 2012 Configuration Manager Service Pack 2

View products that this article applies to.

Symptoms

In a Configuration Manager environment where the management point is configured for HTTPS communication, clients can't contact a Cloud Distribution Point to retrieve package content. Errors that resemble the following are recorded in the DataTransferService.log file on the client computer:

Request to https://clouddp1.clouddp.com:443/downloadrestservice.svc/getcontentxmlsecure?pid... failed with 400
Successfully sent location services HTTPS failure message.
Error sending DAV request. HTTP code 400, status 'Bad Request'
GetDirectoryList_HTTP('https://clouddp1.clouddp.com:443/…') failed with code 0x87d0027e.
Error retrieving manifest (0x87d0027e). Will attempt retry 1 in 30 seconds.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=support

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Cumulative Update 1 for System Center 2012 R2 Configuration Manager Service Pack 1 and System Center 2012 Configuration Manager Service Pack 2.

Restart information

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

Note We recommend that you close Configuration Manager Administration Console before you apply this hotfix package.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

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.

File name	File version	File size	Date	Time	Platform
Contentwebrole.cab	Not Applicable	7,570,454	26-Jun-2015	03:10	Not Applicable
Microsoft.configurationmanager.azureroles.common.utility.dll	5.0.8239.1226	26,800	26-Jun-2015	03:10	x86

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

Note If the BranchCache feature is enabled on the site server that's hosting the package content, the content transfer from the distribution point to the client will continue to fail even after this update is applied. In this situation, errors that resemble the following are recorded in the ContentTransferManager.log file on the client:

Failed to decrypt C:\Windows\ccmcache\{package_filename}

To work around the issue, disable the BranchCache feature on the site server computer that's associated with CloudDP, and then re-update the content on CloundDP.

↑ Back to the top