I think its more for management. There was a server consolidation last year and with the advent of SCCM 2012 they just need the justification for additional servers for DP's....
On Mon, Sep 30, 2013 at 1:30 PM, Jason Wallace <[email protected]> wrote: > I would work on the basis of what service are they willing to give up in > which sites. > > This will start off with having to sacrifice PXE and SMP roles if there is > no server class device in the site. This will likely be a cutoff point for > whether a DP is needed in that site. Given this formula you will likely > find that you need to have a DP well before 100 clients > > Remember however that servers tend to require more management than clients > and you may find that you choose to speak to one of the companies that > specialises in providing service to smaller, hard to reach offices > > ------------------------------ > From: [email protected] > > To: [email protected] > Subject: RE: [mssms] Distribution Points > Date: Mon, 30 Sep 2013 18:18:07 +0000 > > You could use BITS to throttle DPs. > > > > Also take a look at this (echo’s Trevors feedback): > > > > > http://technet.microsoft.com/en-us/library/gg712321.aspx#BKMK_DistributionPointInfrastructure > > > > Consider the following to help you determine the appropriate number of > distribution points to install at a site: > > - The number of clients that might access the distribution point > - The configuration of the distribution point, such as PXE and > multicast > - The network bandwidth that is available between clients and > distribution points > - The size of the content that clients retrieve from the distribution > point > - The setting for BranchCache that when it is enabled, lets clients at > remote locations obtain content from local clients > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jason Wallace > *Sent:* Monday, September 30, 2013 2:11 PM > *To:* [email protected] > *Subject:* RE: [mssms] Distribution Points > > > > There IS no magic formula! Simples > > > > If you are doing OSD then bear in mind that you will be restricted in what > you can / cannot do relative to the larger sites. If you want a "full > service" site down in the tiny offices then you will likely want to speak > to Adaptiva > > > > If you are happy that OSD is going to be something which you work around > then you could certainly use BranchCache in many sites in order to control > bandwidth. > > > > Your figure of 100 clients, for standard software distribution should be OK > ------------------------------ > > From: [email protected] > Date: Mon, 30 Sep 2013 13:03:42 -0500 > Subject: Re: [mssms] Distribution Points > To: [email protected] > > · How many users are at that location? Varies 5 -1000 > > · How large are the packages you’ll be distributing? Normal > packages office..etc > > · Will you be performing OS deployments at that location? Yes > > · How large is the network pipe to the location? varies 512k - 1GB > > There are about 200 locations in that region reporting back to the PS and > I recommended any place over 100 clients would require a DP. They want to > see a magic formula... > > > > > > On Mon, Sep 30, 2013 at 12:55 PM, Trevor Sullivan <[email protected]> > wrote: > > Hello, > > > > You need to evaluate the answers to the following questions, among others: > > > > · How many users are at that location? > · How large are the packages you’ll be distributing? > · Will you be performing OS deployments at that location? > · How large is the network pipe to the location? > > > > Cheers, > > Trevor Sullivan > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *sccmadmin341 > *Sent:* Monday, September 30, 2013 12:53 PM > *To:* [email protected] > *Subject:* [mssms] Distribution Points > > > > Is there a recommend formula available when choosing whether or not to use > a DP for a particular location? > > > > > > > > > > > > >
