ConfigMgr SCCM 2012 SP1 Pull DP Details and Log Files


Pull Distribution point is one of the new features available with ConfigMgr 2012 SP1 RTM  release. What is Pull Distribution Point  ? Enable the  pull  DP option on a DP to change the  behaviour of  how  that  computer obtains the content that you distribute to the DP. When we configure a DP to be a pull DP, we must specify one or more source DPs from which the pull dp obtains the content.

Pull DP configuration  would be very helpful in following scenario. When you’ve a primary server across the WAN (for example in US) and 3 DPs in  India. Out of 3  DPs, one DP is configured as pull DP and specified other   2 DPs in the pull DP to act as “source for content”. When you deploy a   package to ‘pull DP’ and the content is already replicated to any of the other DPs in India then the content won’t get downloaded across the WAN.    One of  the DP which has the content act as “SOURCE for content” for pull DP.

Following are topics covered in this post

1. How to Install/Configure Pull DP?

2. How to Verify the Pull DP is installed successfully?

3. How to confirm whether the Package or application is replicated to PULL DP ?

4. More details a bout Pull DP

How to Install Pull DP?

In CM 2012 console, Navigate to “Servers and Site System Roles” –> Under Site System Roles right click on Distribution Point and go to properties –> Click on “Pull Distribution Point” tab and Select the option “Enable pulling content from other Distribution points”  and you’re done!

(Note : ACNCMPRI is my Primary server.  Pull DP = ACNCMCDP02)

How to Verify the Pull DP is installed successfully?

Go through log files in the following sequence.

hman.log @ Primary Sever ACNCMPRI

Distribution Points of site PRI have changed. Update the DistributionPoints table in the database.

Updated DP [“Display=\\ACNCMCDP02.ConfigMgr.Com\”]MSWNET:[“SMS_SITE=PRI”]\\ACNCMCDP02.ConfigMgr.Com\. DBCRC:7AE1A830,NewCRC:1500BC21,Action:0,PDP:0,PullDP:1

DistMgr.log @ Primary Sever ACNCMPRI

Installing PullDP, check \\ACNCMCDP02.ConfigMgr.Com\SMS_DP$\sms\logs\smsdpprov.log and \\ACNCMCDP02.ConfigMgr.Com\SMS_DP$\sms\bin\\pulldp_install.log

PullDP [“Display=\\ACNCMCDP02.ConfigMgr.Com\”]MSWNET:[“SMS_SITE=PRI”]\\ACNCMCDP02.ConfigMgr.Com\ is marked Installed

PullDp_Install.log @ Remote PULL DP Site System ACNCMCDP02.ConfigMgr.Com

Location of the pulldp_install.log file C:\SMS_DP$\sms\bin\pulldp_install.log

How to confirm whether the Package or application is replicated to PULL DP 

Distmgr.log @ Primary Site ACNCMPRI

Created package transfer job to send compressed copy of package CAS000C4 to distribution point [“Display=\\ACNCMCDP02.ConfigMgr.Com\”]MSWNET:[“SMS_SITE=PRI”]\\ACNCMCDP02.ConfigMgr.Com\.  Transfer root = CAS000C4.PCK.DLT.0.1.

Successfully updated the package server status for [“Display=\\ACNCMCDP02.ConfigMgr.Com\”]MSWNET:[“SMS_SITE=PRI”]\\ACNCMCDP02.ConfigMgr.Com\ for package CAS000C4, Status 3


Sending package info bundle CAS000C4 to PullDP. [“Display=\\ACNCMCDP02.ConfigMgr.Com\”]MSWNET:[“SMS_SITE=PRI”]\\ACNCMCDP02.ConfigMgr.Com\

Generated XML notification for Pull DP ACNCMCDP02.ConfigMgr.Com.

Successfully performed WMI actions on pull DP ACNCMCDP02.ConfigMgr.Com.

Finished sending SWD package CAS000C4 version 1 to distribution point ACNCMCDP02.ConfigMgr.Com

Send Request 2012LPRI~    Job:        JEMZC1ZG  Destination:  ACNCMCDP02.ConfigMgr.Com~    State:      Working   Status:    Success    Action:    None~    Total size: 0       k Remaining: 0       k Heartbeat: 11:59~    Start:      11:59     Finish:    11:59      Retry:          ~    SWD PkgID:  CAS000C4  SWD Pkg Version: 1

smsdpprov.log  Remote Site Server PULL DP – ACNCMCDP02

Location of the log file – SMS_DP$\sms\logs

 [F34][Wed 01/16/2013 11:57:50]:Successfully notified PullDP

[F34][Wed 01/16/2013 11:57:51]:Content ‘Content_ff6ce16f-d89a-490f-afc8-21c4cf1e50b3.1’ for package ‘CAS000C4’ has been added to content library successfully

PullDp.log Remote Site Server PULL DP – ACNCMCDP02

Location of the log files – SMS_CCM\Logs

CPullDPPkgJob::LoadJobFromXML() successfully loaded job.

Successfully verified content info Hash C:\SMS_DP$\ :63D5CE8E5C794D09183FFEB341083CCBA05B69F554B3D1ACA5173B73B6C7A1E7

CPullDPService::ExecuteJobs(). 1 jobs to do.

Unpack FileInfo (C:\SMS_DP$\CAS000C4\Content_ff6ce16f-d89a-490f-afc8-21c4cf1e50b3.1.tar)

Created FullDownload DTS job for package CAS000C4, version 1

Content job Content_ff6ce16f-d89a-490f-afc8-21c4cf1e50b3.1 has downloaded successfully for package CAS000C4, version 1

Package job has completed successfully for package CAS000C4, version 1

More Details about Pull DP here

Enable the pull-distribution point option on a distribution point to change the behaviour of how that computer obtains the content that you distribute to the distribution point. Important: Although a pull-distribution point supports communications over HTTP and HTTPS, source distribution points must be configured for HTTP. You cannot specify a source distribution point that is configured for HTTPS.
When you distribute content to the pull-distribution point, notifies the distribution point about the content but does not transfer the content to the distribution point computer. Instead, after the pull-distribution point is notified, it attempts to download the content from the first source distribution point on its list of source distribution points. If the content is not available, the pull-distribution point attempts to download the content from the next distribution point on the list, continuing until either the content is successfully downloaded or the content is not accessed from any source distribution point. If the content cannot be downloaded from any source distribution point, the pull-distribution point sleeps for 30 minutes and then begins the process again.
To manage the transfer of content, pull-distribution points use the CCMFramework component of the client software. This framework is installed by the Pulldp.msi when you configure the dP  to be a pull-distribution point and does not require that the client be installed. After the pull- dp installs, the CCMExec service on the distribution point computer must be operational for the pull-distribution point to function. When the pull-distribution point transfers content, it logs its operation the datatranasferservice.log and the pulldp.log on the distribution point computer.
By default, a pull-distribution point uses its computer account to transfer content form a source distribution point. However, when the pull-distribution point transfers content from a source distribution point that is in a remote forest, the pull-distribution point always uses the Network Access Account. This requires that the computer have the client installed and that a Network Access Account is configured for use and has access to the source distribution point. For information about the Network Access Account, see the Network Access Account section in the Technical Reference for Accounts Used in Configuration Manager topic. For information about configuring the Network Access Account, see Configure the Network Access Account in the Configuring Content Management in Configuration Manager topic.
Because the pull-distribution point requires the CCMFramework from SP1, computers that run client software from with no service pack cannot be configured as pull-distribution points.
You can remove the configuration to be a pull-distribution point by editing the properties of the distribution point. When you remove the pull-distribution point configuration, the distribution point returns to normal operation and future content transfers to the distribution point are managed by the site server. In the console, there is nothing that identified the distribution point as a pull-distribution point. You must review the properties of the distribution point to identify if it is configured as a pull-distribution point.


  1. Our infrastructure have recently been updated to be on SCCM 2012 R2. we have more than 10 remote dp in our environment. Weird thing is I cannot see any Pull distribution tab like you explained in your article. Do I need to enable anything from the Central Server or something need to be installed or enabled from the DP server itself?

  2. Hi Anoop, We have a scenario where we want to introduce additional primary servers in another connected DC and configure all the existing dp’s to take updates from the new primary servers. Wondering what needs to be done here ?

    • Hi ! – Does that mean primary server is in another forest and both the forests don’t have two way trust? By default, a pull-distribution point uses its computer account to transfer content form a source distribution point. However, when the pull-distribution point transfers content from a source distribution point that is in a remote forest, the pull-distribution point always uses the Network Access Account.

  3. Hi Anoop – Definitely enjoy your novelty of SCCM write ups, keep up the good work!
    My question is working with VSAT connections. Not sure how much you’ve worked with customers around this but I will ask anyways, opinion if you will. We are using 1 Primary with 37 DPs mixed Windows 7 boxes and Server 08 R2 for PXE purposes. MP and SUP roles are on the same server if that is necessary to know.

    Here we are in Oil & Gas and rather difficult getting content distribution over low bandwidth – high latency connections (500-600+ms some up to 1200+ms) to our Rig platforms over VSAT especially Windows Updates. To overcome this minor issue, since my connection from Primary pushing content to Remote offices is just fine, could I take each of the Rig DPs onboard and turn those into Pull DPs selecting the Remote Office DP as the Source in the nearest Region oppose to the Primary which is where the Rig DPs get it from now. BITs Throttling, since my SCCM DPs have Clients, can’t I use Client Settings targeting the Collection of Pull DPs since the Rate Limit tab goes away, if I understand correctly?

    I.E. Primary server is in the US, DP in the South East Asia Office and wanted the Content distribution for the Rigs offshore to get it from the Office DP and not from the Primary…
    Thoughts that this might help? Hopefully I am thinking this Pull Distribution process correctly, if not suggest any other way to help this scenario? BranchCache maybe, but then again content has to go over VSAT at least once at the same package size and rate so I am not sure where that would help greatly.

    • Hi Eric ! – I Never worked with VSAT however from SCCM perspective it’s same, isn’t it ? It just increases the hop to reach the client machines. The technologies (pull DP, BranchCache) which you mentioned are good ….however I think, they are not very robust and missing the touch of enterprise class at the moment. Have you tried third part content providers like Adaptiva OneSite or 1E in this scenario? I would suggest to go for third party content providers …

  4. Thanks for the prompt feedback. Unfortunately, 3rd party is out of the question at this time due to budget constraints. I will do testing on a DP configured for Pull DP and report anything worthy.


Please enter your comment!
Please enter your name here