Re: 400 remote sites connected via DSL

I have 400 branch offices connected via DSL (mostly 144kbps) with about 5
machines in each office.

Are you saying that it would be more reliable and efficient if I set the GPO
for BITS throttling on each client and let them all contact the distribution
point (download and execute) at the central site over the WAN?

This would be almost 2000 machines contacting the central site distribution
point and downloading their packages as opposed to 400 distribution points
housing the packages and then having each branch have it's own distribution
point?

That would be much simpler (having one distribution point to manage instead
of 400).

I'm running a 100MB package distribution to a test office's "server share".
Once I'm done, i'm going to get the bandwidth statistics. I will try your
way distributing to the clients directly from the central site's distribution
point and see what happens.

It just doesn't seem logical. 400 WAN links with a DP in each office or
2000 roaming clients downloading from remote distribution points.

"Steve Thompson" wrote:

Hi Nick,

As with solving any problem there are numerous solutions. Wherever possible,
I strive for simplicity and supportability.

The primary problem with remote distribution points (or file shares),
packages are sent uncompressed from site server to the remote distribution
points with *no* bandwidth control. The potential exists to saturate your
WAN with one large update, i.e.XP SP2.

If these dp's are all connected to one sms site, there will be issues with
the number of threads allocated for package distrubution, and the time it
takes to perform a distribution.

The only other option I can think of, besides Branch Nomad, or SCCM 2007
Branch Distribution Points, would be BITS throttling.

Some ideas for you; use Group Policy, and/or registry settings to restrict
the amount of bandwidth that BITS uses, then use the download & execute
setting for all advertisements.

Steve

"Nick SMS Administrator - Detroit, Mi"
<NickSMSAdministratorDetroitMi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6C36B5F4-1653-4038-827D-CF95AE53E6C1@xxxxxxxxxxxxxxxx
Steve,
Thanks for your response. I still don't know why I shouldn't setup 400
distribution points.

You said: " I would not go that route, I believe that it will become very
difficult to manage..."

How else can I control without purchasing something like the SMSNomad
Branch
software. I was quoted 7.50 a license in packs of 500 licenses and I'm
looking to do this for free, so I can't purchase a solution.

I was able to setup an XP pro machine as an SMS "server share" site system
with the protected distribution point role. I think I'm all set now, but
your comment made me cast some doubt if I'm missing something here.

How else could I setup 400+ branch offices with no servers, only xp
machines
connected to slow links?

"Steve Thompson" wrote:

"Nick SMS Administrator - Detroit, Mi" <Nick SMS Administrator - Detroit,
Mi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EA22C089-887F-40D9-A435-C3A674A64CFA@xxxxxxxxxxxxxxxx
SMS 2003 SP2

400+ remote locations connected via DSL lines of which the majority are
only
144Kbs.

5 clients (at most) in each site.

I am planning on deploying ITMU to all clients by setting up one client
at
each remote site (roaming boundary) as a software distribution point
(server
share).

The control of bandwidth throttling is only available for secondary
sites.
I do not think it would be a good idea to set over 400 secondary sites
up
just for this feature.

2 questions.

1. Is setting up over 400 Server Shares a good idea.
2. If setting up that many server shares is okay, how can I throttle
the
bandwidth.

Hi Nick,

Just replied to your other post in this group
'microsoft.public.sms.swdist'

I would not go that route, I believe that it will become very difficult
to
manage...

Steve






.

Relevant Pages

  • Re: SMS 2003 Installation & Configuration Question
    ... Assuming an even distribution of clients, ... I run SMS and SQL Server on the same ...
    (microsoft.public.sms.setup)
  • Re: SMS2 SP5 Site Status Incorrect
    ... >> If I reinstall SMS entirely, ... >> all the clients need deinstalling and then reinstalling ... >> from the new server? ...
    (microsoft.public.sms.setup)
  • Re: 400 remote sites connected via DSL
    ... The network admin wasn't monitoring the same network. ... distribution point server share. ... If the SMS server is getting hit by all the clients at once, ...
    (microsoft.public.sms.swdist)
  • Re: Outlook 2k7 and Ex2k7 -> 0X80190197
    ... Outlook 2007 clients will use the proxy settings that are in IE or used in the WinAPIs. ... In addition to this you can check to see which mailbox store you are on and then look at the configuration for that OAB in the Offline Address List container. ... See if this OAB is configured for PF distribution, ... There are several potential advantages of the new distribution mechanism including supporting more concurrent clients, reduced bandwidth usage, and more control over the distribution points. ...
    (microsoft.public.exchange.admin)
  • Re: 400 remote sites connected via DSL
    ... the machines only care about their own personal available bandwidth. ... If the SMS server is getting hit by all the clients at once, ... This would be almost 2000 machines contacting the central site distribution ...
    (microsoft.public.sms.swdist)