Concurrent download from PullDPs on a single site server

Hi,

Im trying to understand the impact of PullDPs on the network.
Ive looked on TechNet with no success to get the answer to the following question :

How many PullDP can download a package at the same time, from a single site server (primary server with DP)?

I think I found the answer when distributing a small package to 200+PullDP at the same time.
In the PkgXferMgr.log, on the primary server, I see the following entry :

PullDP download in progress . queried count = 6/100

Does that mean that a maximum of 100 PullDP can download a package at the same time?

The package is really small, so I can see, while this entry come back from time to time in the log with a different queried count, that the success of distribution goes up slowly on my package.
If the package was bigger, I presume that this count would go much higher than this.

Is that correct?

Is there a way to modify the limit of concurrent PullDP download?(in or out of console)

I plan on having ~1200PullDP, all with the same source DP, which is my primary server.
So I really need to understand that process completely to not load the network while transferring packages.
I understand that my server must have excellent resources in order to support that.

thanks


May 20th, 2015 3:08pm

How many DPs at a time are regulated through configuration of Concurrent distribution settings

https://technet.microsoft.com/en-au/library/gg712321.aspx

You may also find some useful insights at the following blog post:

http://blogs.technet.com/b/configmgrteam/archive/2013/06/06/introducing-the-pull-distribution-points.aspx

Finally, you plan on having ~1200 Pull DP with the same source DP. There is a specific warning at this Technet note: https://technet.microsoft.com/en-us/library/gg682077.aspx

WarningWarning 

The number of pull-distribution points that one source distribution point can support similarly depends on the speed of the network and hardware configuration of the source distribution point computer, but is also affected by the amount of content you have deployed. This is because unlike clients that typically access content at different times over the course of a deployments window, all pull-distribution point request content at the same time and can request all available content and not just the content that is applicable to them, as would a client. When too much of a processing load is placed on a source distribution point, this can cause unexpected delays in distributing the content to the expected distribution points in your environment.

Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 12:38am

How many DPs at a time are regulated through configuration of Concurrent distribution settings

https://technet.microsoft.com/en-au/library/gg712321.aspx

This is incorrect, see the note on the same page: "The process to download content by the pull-distribution point is the same as is used by Configuration Manager clients. For the transfer of content by the pull-distribution point, neither the concurrent transfer settings, nor the scheduling and throttling options that you configure for standard distribution points are used."
May 22nd, 2015 9:13am

Thanks Jason. I do stand corrected there
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 8:51pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics