1 voteJonathan Lefebvre-Globensky shared this idea ·
317 votesplanned · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
on our short term radar.
20 votesNoted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
The best way to control this is make a mesh of pull-DPs, and have some pull from other DPs… as opposed to all from the siteserver. That offloads network bandwidth from the siteserver
An error occurred while saving the commentJonathan Lefebvre-Globensky commented
Thanks for the suggestion. In scenario like in Retail, it some time can't be possible as all store (pullDP) communicate only with the head office. Additionnal note : it could be only better known process of how all this is processed. I've seen difference on how SCCM 2012 R2 and 2012 R2 SP1 handle large distribution.
In 2012 R2 : it seemed like concurrent sending was stock at around 70 PullDP.
In 2012R2 SP1 : it seems more like all or close to for concurrent sending.
PS : I,ve followed the distribution in the content status