Pull DP (Distribution Point) is one of the new features available with the ConfigMgr 2012 SP1 RTM release. What is Pull Distribution Point? Enable the pull DP option on a DP to change the behavior 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
DistMgr.log @ Primary Sever ACNCMPRI
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
PkgXferMgr.log SMS_PACKAGE_TRANSFER_MANAGER @ Primary Site – ACNCMPRI
smsdpprov.log Remote Site Server PULL DP – ACNCMCDP02
Location of the log file – SMS_DP$\sms\logs
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$\CAS000C4.tz :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 hereEnable 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. Note: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.