By providing this settings, it would ease up massive distribution of a package to many PullDP.
A setting similar to Concurent download on DP would be perfect!
As of now, updating a package hosted on 1000 PullDP will trigger all PullDP at the same time to update the package.
This cause high CPU and IO on the server as well as potential network load.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
When monitoring a DP that has multiple package failures, you have to go to the DP>Content Tab and search for the failed packages individually, or go to the package and Right click>Redistribute on each DP. When you see 10 failed packages when looking at the DP at \Monitoring\Overview\Distribution Status\Distribution Point Configuration Status, a "Redistribute" action right there in the message view would be awesome!!29 votes
If a Distribution Point server or server hosting the Content Location is restarted, the content transfer is not resumed to the Distribution Point. The content transfer should resume to the Distribution Point after the restart is complete.11 votes
- Don't see your idea?