Justin Gao's Technical World

About Infrastructure, Management, Security, Virtualization, Cloud and Unified Communication , Welcome!

You Need to Know : How to configure System Center 2012 R2 Configuration Manager Pull-Distribution Point

You Need to Know : How to configure System Center 2012 R2 Configuration Manager Pull-Distribution Point

  • Comments 5
  • Likes

   Hi All :

   Beginning with Configuration Manager SP1, you can configure a distribution point that is not on a site server to be a pull-distribution point. When you deploy content to a large number of distribution points at a site, pull-distribution points can help reduce the processing load on the site server and can help to speed the transfer of the content to each distribution point. This efficiency is achieved by offloading the process of transferring the content to each distribution point from the distribution manager process on the site server. Instead, each pull-distribution point individually manages the transfer of content by downloading content from another distribution point that already has a copy of the content. A pull-distribution point can only obtain content from a distribution point that is specified as a source distribution point.

   Pull-distribution points support the same configurations and functionality as typical Configuration Manager distribution points. For example, a distribution point that is configured as a pull-distribution point supports the use of multicast and PXE configurations, content validation, and on-demand content distribution. A pull-distribution point supports HTTP or HTTPS communications from clients, supports the same certificates options as other distribution points, and can be managed individually or as a member of a distribution point group. However, the following configurations are exceptions to support for the pull-distribution point:

  • A cloud-based distribution point cannot be configured as a pull-distribution point. Similarly, a cloud-based distribution point cannot be used as a source distribution point.
  • A distribution point on a site server cannot be configured as a pull-distribution point.
  • The prestage content configuration for a distribution point overrides the pull-distribution point configuration. A pull-distribution point that is configured for prestaged content waits for the content. It does not pull content from source distribution point, and, like a standard distribution point that has the prestage content configuration, does not receive content from the site server.
  • A distribution point that is configured as a pull-distribution point does not use configurations for rate limits when it transfers content. If you configure a previously installed distribution point to be a pull-distribution point, configurations for rate limits are saved, but not used. If, at a later time, you remove the pull-distribution point configuration, the rate limit configurations are implemented as previously configured. 
  • A distribution point that is configured as a pull-distribution point does not use the Retry settings for content distribution. Retry Settings can be configured as part of the Software Distribution Component Properties for each site. To view or configure these properties, in the Administration workspace of the Configuration Manager console, expand Site Configuration, and then select Sites. Next, in the results pane, select a site, and then on the Home tab, select Configure Site Components, and then select Software Distribution. The following sequence of events occurs when you distribute software to a pull-distribution point:
    • As soon as content is distributed to a pull-distribution point, the Package Transfer Manager on the site server checks the site database to confirm if the content is available on a source distribution point. If it cannot confirm that the content is on a source distribution point for the pull-distribution point, it repeats the check every 20 minutes until the content is available.
    • When the Package Transfer Manager confirms that the content is available, it notifies the pull-distribution point to download the content. When the pull-distribution point receives this notification, it attempts to download the content from its source distribution points.
    • After the pull-distribution point completes the download of content, it submits this status to a management point. However, if after 60 minutes, this status is not received, the Package Transfer Manager wakes up and checks with the pull-distribution point to confirm if the pull-distribution point has downloaded the content. If the content download is in progress, the Package Transfer Manager sleeps for 60 minutes before it checks with the pull-distribution point again. This cycle continues until the pull-distribution point completes the content transfer.
  • To transfer content from a source distribution point in a remote forest, the computer that hosts the pull-distribution point must have a Configuration Manager client installed. A Network Access Account that can access the source distribution point must be configured for use.

    The attached document will to show you how to installing and configure a DP being a Pull-DP.

 

    Please use Adobe Reader X or above version to open!

 

    Enjoy!

    Justin Gao

    Microsoft (China)

Attachment: SC2012 R2 ConfigMgr RTM Pull DP Operation Document.pdf
Comments
  • very useful, Thanks !

  • I'm having issues with this in our environment: "After the pull-distribution point completes the download of content, it submits this status to a management point. However, if after 60 minutes, this status is not received, the Package Transfer Manager wakes up and checks with the pull-distribution point to confirm if the pull-distribution point has downloaded the content." The Pull DP is sending the status to the MP successfully, so says the logs on the Pull DP, but the MP must not be receiving the status update or something because it takes an hour before the completed status is updated in the console meaning the PkgXferMgr is having to go back out and check on the status to update. Why is this? Why isn't the Pull DP updating the MP successfully even though the PullDP.log has the following lines: Report state message 0x00000001 to MP PullDP 1/9/2014 12:47:10 PM 732 (0x02DC) Report Body: AMD0000B["Display=\\svr-1235.company.com\"]MSWNET:["SMS_SITE=AMD"]\\svr-1235.company.com\{714F6ACD-B380-4C4A-9921-C81E076FDD42} PullDP 1/9/2014 12:47:10 PM 732 (0x02DC) In SSL, but with no client cert PullDP 1/9/2014 12:47:10 PM 732 (0x02DC) CPullDPResponse::ReportPackageState return value 0x00000000. PullDP 1/9/2014 12:47:10 PM 732 (0x02DC) The DataTransferService.log has the following lines: DTSJob {4BB835FC-D074-43EA-B29F-FFF5402CA99D} in state 'DownloadingData'. DataTransferService 1/9/2014 12:46:54 PM 732 (0x02DC) DTSJob {4BB835FC-D074-43EA-B29F-FFF5402CA99D} in state 'RetrievedData'. DataTransferService 1/9/2014 12:47:08 PM 2344 (0x0928) DTSJob {4BB835FC-D074-43EA-B29F-FFF5402CA99D} successfully completed download. DataTransferService 1/9/2014 12:47:08 PM 2344 (0x0928) DTSJob {4BB835FC-D074-43EA-B29F-FFF5402CA99D} in state 'NotifiedComplete'. DataTransferService 1/9/2014 12:47:08 PM 4452 (0x1164) DTS job {4BB835FC-D074-43EA-B29F-FFF5402CA99D} has completed: Status : SUCCESS, Start time : 01/09/2014 12:46:54, Completion time : 01/09/2014 12:47:08, Elapsed time : 14 seconds DataTransferService 1/9/2014 12:47:08 PM 4452 (0x1164) Is there a setting in IIS or a log somewhere on the MP that I can reference that might help in diagnosing the issue?

  • Forgot to sign in before posting that - ^ was me..

  • Hi mchippy: Your environment is in the SSL mode ? The log indicate "In SSL, but with no client cert PullDP". And are you confirm the PullDP had already downloaded contents?

  • thanks

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment