Re: 400 remote sites connected via DSL
- From: "Steve Thompson" <stevethompson@xxxxxxxxxxxxx>
- Date: Tue, 2 Jan 2007 15:48:46 -0500
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
.
- Follow-Ups:
- Re: 400 remote sites connected via DSL
- From: Nick SMS Administrator - Detroit, Mi
- Re: 400 remote sites connected via DSL
- References:
- Re: 400 remote sites connected via DSL
- From: Steve Thompson
- Re: 400 remote sites connected via DSL
- From: Nick SMS Administrator - Detroit, Mi
- Re: 400 remote sites connected via DSL
- Prev by Date: Re: package not loading/updating
- Next by Date: Re: 400 remote sites connected via DSL
- Previous by thread: Re: 400 remote sites connected via DSL
- Next by thread: Re: 400 remote sites connected via DSL
- Index(es):
Relevant Pages
|
