I’m not sure why the DP is showing rate limits as “Yes”, maybe try setting a rate limit, then toggle back to unlimited and see if “Rate Limits” changes to no.
When the pull-distribution point transfers content, it transfers content by using Background Intelligent Transfer Service (BITS). If you have a need to throttle or schedule your download times and bandwidth you would need to configure BITS settings on the pull-distribution points. You can configure BITS settings on pull-distribution points by using: · Configuration Manager console: Use the Client Settings option in the Administration workspace (you would need the Configuration Manager client installed on your pull-distribution point computer; this won’t work without the Configuration Manager client) · Group policy settings: Use this option if you don’t have a Configuration Manager client installed on the pull-distribution point computer. Here are a few good articles on Pull-DPs: Introducing the Pull-Distribution Points: http://blogs.technet.com/b/configmgrteam/archive/2013/06/06/introducing-the-pull-distribution-points.aspx Planning for Pull-Distribution Points: http://technet.microsoft.com/en-us/library/gg712321.aspx#BKMK_PlanPullDps Jerry From: [email protected] [mailto:[email protected]] On Behalf Of Mitchell, Steven R Sent: Tuesday, August 19, 2014 10:25 PM To: [email protected] Subject: RE: [mssms] rate limit question Ok several hundred is just what it feels like. We have about 200 dps. Some are on secondary sites. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mike Dzikowski Sent: Tuesday, August 19, 2014 7:59 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] rate limit question Also, When you say several hundred DPs....How many DPs does your primary site currently have? http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigClientNumbers • System Center 2012 Configuration Manager with no service pack ◦ Each primary and secondary site supports up to 250 distribution points. ◦ Each distribution point supports connections from up to 4,000 clients. • System Center 2012 Configuration Manager with SP ◦ Each primary and secondary site supports up to 250 distribution points. ◦ Each distribution point supports connections from up to 4,000 clients ◦ A pull-distribution point is considered to be a client when it accesses another distribution point to obtain content. • System Center 2012 R2 Configuration Manager ◦ Each primary and secondary site supports up to 250 distribution points. ◦ Each primary and secondary site supports up to 2000 additional distribution points configured as pull-distribution points. For example, a single primary site supports 2250 distribution points when 2000 of those distribution points are configured as pull-distribution points. ◦ Each distribution point supports connections from up to 4,000 clients. ◦ A pull-distribution point is considered to be a client when it accesses another distribution point to obtain content. Mike D- ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] rate limit question Date: Tue, 19 Aug 2014 19:36:05 -0500 Steven, Have you configured your Distribution Points as Pull Distribution Points? You might want to consider doing this, to help speed up content distribution. Are you on Configuration Manager 2012 R2? What do you mean the console shows rate limits as being set, but you haven’t configured any rate limits? What does your sending thread configuration look like on the Primary Site? Cheers, Trevor Sullivan Microsoft PowerShell MVP [cid:[email protected]]<http://mms.mnscug.org/> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mitchell, Steven R Sent: Tuesday, August 19, 2014 7:12 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] rate limit question All, We have been struggling with deploying packages in our environment. We have a single primary site and several hundred DP’s. The thing is that it seems like all my systems are taking forever to replicate even the smallest packages. I have no rate limits set which would force single threading but when I look in the console the DP’s are showing that there is a rate limit set on every dp except the secondary sites. Does anyone have any idea about this at all? The performance seems much slower than our 2007 environment was. Any thoughts? Steven ________________________________ CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may contain confidential and privileged information protected by law. If you received this e-mail in error, any review, use, dissemination, distribution, or copying of the e-mail is strictly prohibited. Please notify the sender immediately by return e-mail and delete all copies from your system.
