Re: Design Planning-Primary/secondary setup

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

You state that "And to finish installing local mp's without installing
secondary sites would not be an options since you can only have one mp per
site." I thought that you could put multiple management points on various
computers in each site even if not site system.


"Kim Oppalfens" wrote:

> I'll second Steve.
> Congested links really require secondary sites because of the extra
> bandwidth control & compression you get.
> And again as Steve already mentioned Secondary site server licenses are free
> of charge.
>
> And to finish installing local mp's without installing secondary sites would
> not be an options since you can only have one mp per site. (Unless you plan
> to use NLB clusters across congested wan links :-)
>
> --
> Kim Oppalfens
> Telindus Belgium
> MVP Windows Server System - SMS
> "Steve Thompson" <stevethompson@xxxxxxxxxxxxx> wrote in message
> news:eRCbl%23NyFHA.2800@xxxxxxxxxxxxxxxxxxxxxxx
> > "Preston" <Preston@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:827BF709-1A4F-4320-9F2E-1A41C716E9DC@xxxxxxxxxxxxxxxx
> >> We have 187 sites. Planning on doing 1 Central with 6 primary (regional)
> >> child sites. We have 180 locations that could be split regionally under
> > the
> >> primary sites as in primary parent with 30 child secondary sites beneath
> > eacg
> >> therefore split pretty evenly. The links are very slow and congested
> >> already with about 5 to 100 people per location. Seems ridiculous to
> >> have
> >> these 180 secondary sites with such low quantity of users. The question
> > is
> >> whether it is better to have the secondary sites at each of these 180
> >> locations or just have the 5-100 users each just report to their regional
> >> primary site and omit the making of secondary sites? With omitting the
> >> secondary site creation, we could like to maybe put Management points on
> >> server local to that location and distribution point as well local.
> >> Would
> >> there be a way to make sure clients would use local distribution point
> > only
> >> and also talk through local MP? Then the MP would contact upline Site
> >> Server. We most definately want the clients to get software locally.
> >> Advanced clients will be our primary base of users. Not sure if more
> > traffic
> >> would be generated from having Secondary site servers at 180 locations
> > versus
> >> users not having local secondary site server at these locations.
> >>
> >> What do you think?
> >
> > Went through a very similar design at my old company (it was SMS 2.0), but
> > the implications are the same.
> >
> > New with SMS 2003, is the concept of protected distribution points...
> > however, with SMS 2003 and no license fees charged for secondary sites, I
> > do
> > not see a downside to your design of regional child sites (even with < 10
> > clients), each with 30 secondary sites. This design served us well. Keep
> > in
> > mind to create a local MP, you'd need to create a secondary site at that
> > remote location. You'll get additional efficiencies such as sender
> > bandwidth
> > controls between the child site and each secondary site. There will be
> > some
> > communication between the adv client and the parent, child site -- however
> > if you enable a management point proxy on each secondary you'll get
> > efficiencies with policies being cached on the secondary site; and
> > inventory
> > information collected by the secondary and sent to the parent.
> >
> > Steve
> >
> >
>
>
>
.

Relevant Pages

  • Re: Design Planning-Primary/secondary setup
    ... I'll second Steve. ... And again as Steve already mentioned Secondary site server licenses are free ... And to finish installing local mp's without installing secondary sites would ... We most definately want the clients to get software locally. ...
    (microsoft.public.sms.setup)
  • Re: Design Planning-Primary/secondary setup
    ... > primary sites as in primary parent with 30 child secondary sites beneath ... > these 180 secondary sites with such low quantity of users. ... We most definately want the clients to get software locally. ... controls between the child site and each secondary site. ...
    (microsoft.public.sms.setup)
  • 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)