Re: 400 remote sites connected via DSL


I say wait till sms v.4 there's a new feature called branch distribution
points, basically makes a computer at a site a distribution point. From
microsoft:

Branch Distribution Points

A new SMS server role, the branch distribution point, allows small office
locations to host SMS packages on workstation computers without requiring a
SMS secondary site. Packages transfer to the branch distribution point
according to bandwidth controlled settings using BITS (Background Intelligent
Transfer Service).


"Nick SMS Administrator - Detroit, Mi" wrote:

My Test failed. The network admin wasn't monitoring the same network. I'm
setting up a new lab to test in today.


"Nick SMS Administrator - Detroit, Mi" wrote:

Right now (production), I have one central site server serving the roles of
MP, SLP, and DP. All the clients at the remote sites are installed and
reporting back. I'm just not distributing software yet.

I also have every site as a collection based on system-resource>ip subnet.

I also have 1 test environment that is setup just like one of our 5-computer
branch networks. The test environment is a 144Kbps connection back to
headquarters. I'm waiting for our network admin to send me the statistics
from my test last night. I set one of the test xp pro machines up as a
distribution point server share.

"Steve Thompson" wrote:

How many distribution points do you have defined for your site?

"Nick SMS Administrator - Detroit, Mi"
<NickSMSAdministratorDetroitMi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:885C33E0-746E-4762-BF2D-77BA8E2E7AF0@xxxxxxxxxxxxxxxx
One other thing. If I throttle the bandwidth on the BITS Client for each
machine, the machines only care about their own personal available
bandwidth.
If the SMS server is getting hit by all the clients at once, I don't think
the network card could handle all those requests and I think the server
would
crash. (I thought I read that somewhere).

"Nick SMS Administrator - Detroit, Mi" wrote:

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: Inplace Upgrade os SMS2.0 to 2003
    ... But there is no automated way of comparing ... > the distribution points so I know which ones need updating? ... >>> Client Access Point, Component Server, Distribution Point, Site Server and ... >>> another server that is being used as a SMS Distribution Point. ...
    (microsoft.public.sms.setup)
  • Advanced Client workstations not Connecting to local Dist. points
    ... I have a problem with distributing packages from local distribution points. ... Currently I am pushing out Service Pack 2 for Windows XP with SMS 2003. ... program will start once the download has been successfully completed. ... SERVER1 is the SMS Primary SITE SERVER ...
    (microsoft.public.sms.swdist)
  • Re: SMS Distribution point
    ... point with image packages but using a usb drive or a DVD or similar external ... Windows Server System MVP - SMS ... Stop the distribution manager component. ...
    (microsoft.public.sms.admin)
  • Re: Server Share and Distribution Point
    ... A server does not need SMS installed to be assigned the DP site system ... > We're running a test lab to evaluate SMS 2003. ... > With regards to distribution points, we noted in some whitepaper stating ...
    (microsoft.public.sms.swdist)
  • Re: Distribution Manager - Error 2302
    ... SMS 2003 Scenarios and Procedures Planning and Deployment Guide: ... > -Seventythree SECONDARY SITES reporting to one of the PRIMARY SITES. ... > a Server Share for a Distribution Point. ...
    (microsoft.public.sms.admin)
Loading