Re: 400 remote sites connected via DSL

"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: How to design?
    ... I agree with the general recommendation of having secondary sites in the ... remote offices, but this post requires some corrections. ... The fact that this allows clients to connect to a local mp for policies ... >>I want that SMS manage the clients in the child domains. ...
    (microsoft.public.sms.setup)
  • Re: new sms installation
    ... other clients over WAN ... I am brand new to SMS and still trying to grasp it. ... Secondary sites do not require a database, ... hosted on the same sql server.. ...
    (microsoft.public.sms.setup)
  • Re: Upgrade Questons
    ... I think I would upgrade SQL first, but I guess that is just my personal ... preference because I know more about sms than about sql. ... > resources which would now include the resources from the secondary sites. ... clients cannot be assigned to secondary sites anyway. ...
    (microsoft.public.sms.setup)
  • Migration Questions
    ... Collections are populated using site codes. ... Upgrade Central Site to SMS 2003 ... Clients in the secondary sites are still SMS 2.0 clients ...
    (microsoft.public.sms.admin)
  • Re: Advertisement status not reported correctly
    ... SMS 2003 Resource Page: ... > basic (like 'all clients at the central site') or it could be something ... >> software to all the computers (primary and secondary sites), ... >> site have an advertisement status informing that the deployment is OK. ...
    (microsoft.public.sms.swdist)