Distribution Points are by default NOT assigned the same priority
When a new Distribution Point (DP) whether it is a normal DP or a Pull DP is installed to a ConfigMgr 2012 R2 site, the priority assigned to this new DP is always the same by default.
REQUEST FOR CHANGE
It is often desired that Pull DPs are by default assigned lower priority than the normal DPs.
When operating a site with many (hundreds of) DPs installed, the normal DPs serve as source distribution points for the Pull DPs. It is therefore desired, that those normal DPs will have the new package files copied over before the Pull DPs are given instructions to try retrieve the content from those source DPs. Or at least it is expected that the file copy jobs for the source DPs will be created before the instructions to retrieve the files are created for the Pull DPs. This could be accomplished by letting Pull DPs by default have lower priority than normal DPs.
Another way to accomplish an "intelligent" default priority would be to look at dependencies such that a DP that is configured to retrieve the contents from one or more other DPs will by default have lower priority than those DPs.
Pull DPs are given lower distribution priority compared to regular DPs.
See here for more details:
Will Locke commented
In response to the question in the linked Twitter post, please make the Priority setting on DPs a configurable setting via the UI. We have over 1300 DPs, most of which are PullDPs so we don't need secondary sites. However, most of the servers start with numbers, while our source DPs follow a different naming convention. What that means is if we update a package that is already distributed everywhere, it adds the DPs to the queue in alphabetical order so our source DPs get added last. We've been struggling with that for over a year. If the Priority setting via WMI fixes that problem, then it would have been great for us to have had a UI setting where we could have fixed this a long time ago. As it is, I came here to request this feature when I found the link posted above. Otherwise I wouldn't have known about this at all. Don't hide settings behind WMI or powershell which don't exist in the console. I don't have time to learn every obscure WMI setting or powershell cmdlet. Those things should be aids for perform batch processes, not the primary method to operate.
Eric Benda commented
I do not see this intelligence for DPs happening in 1606. We have 400+ DPs and are moving to make most of them pull DPs to reduce the load on our site server.
If pull DPs are in same distribution point group as the source DP, I see all the DPs getting instructions at the same time. I also often see pull DPs in the job queue manager with numerous retries while they wait for their source DP(s) get content. Eventually their source gets the package and the retrying DPs start getting the content.
We have resorted to creating distribution point groups just for the source DPs and distributing to those first. We then distribute to distribution point groups that contain the pull DPs after verifying that the source DPs have the content. This prevents the job queue from filling up with pull DPs waiting for their source to get content.
I agree that pull DPs should automatically be assigned a lower priority when they are configured.
Alex Schneider commented
I know this is an old thread, but I have noticed that the behavior you describe is not occurring with SCCM 2012 R2 SP1 w/ CU3. When I distribute a package to source and pull DPs at the same time, the pull DPs immediately get a notification to attempt to download the content from the source DPs which also have not yet been able to download the content.
I too would like the ability to permanently adjust the DPPriority setting, as that seems to be the best way to control how content distribution is branched out, especially for those of us who have large numbers of DPs.
If I need to open a new request to reiterate the desire for this change, let me know and I will do so.
Jim Walker commented
Please re-introduce or fix the DPPriority setting for Distribution Points. All of us have DP's that are more critical than others, that we want content to get to first.