Re: SMS 2003 Hierarchy Design


Their sms admin console would have to connect over the wan link to the
America site to do any management.

Besides that you will create quite some overhead in collection
configuration and security to make sure they can only manage their
systems.

I advise you to install proxy management points, since they are low
maintenance, low performance requirement roles that provide much better
wan traffic control.

Adding a central site later would be no problem, but you would have to
re-add all packages to this central location afterwards if you want them
to be deployed from there.

Kim Oppalfens
MVP SMS
In article <5346C5A3-57D3-4353-921B-1112E090394D@xxxxxxxxxxxxx>,
Kane@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> Thanks for the reply.
>
> Couldn't I give my Europe and Asia admins access to the America Primary
> server to allow them to manage their systems? Instead of giving them their
> own primary server. What management benefits will they gain from having
> their own primary server?
>
> All of my secondary sites have at least one server. Therefore, the plan was
> to make them all secondary sites. As long as secondary site servers do not
> need to be dedicated to SMS, I should be fine. If I choose to do this I will
> of course setup distribution points at each secondary site, but do you
> recommend setting up proxy management points at each secondary site as well?
>
> As for the Central site, I would really like to avoid maintaining an
> additional server. Could I skip the additional primary server at
> headquarters initially and add it later if necessary?
>
>
> "Kim Oppalfens" wrote:
>
> > In article <A3BBAD4C-C1DA-40F7-BD13-5EC55DB65D20@xxxxxxxxxxxxx>,
> > Kane@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> > > Hello, I'm looking for some help with my SMS hierarchy design.
> > >
> > > I have 21 locations globally which include the following.
> > >
> > > Main American Location (Headquarters) = 800 clients
> > > Main European Location = 100 clients
> > > Main Asian Location = 80 clients
> > > 5 additional American locations each with 50 - 250 clients
> > > 5 additional European locations each with 10 - 200 clients
> > > 8 additional Asia Pacific locations each with 10 - 100 clients
> > >
> > > Bandwidth at each location ranges between 256k and 2MB.
> > >
> > > SMS management is needed at each of the 3 main locations. Headquarters
> > > needs to be able to manage all systems globally and the asia and europe main
> > > locations need to be able to manage the asia and europe remote locations
> > > respectively.
> > >
> > > I originally planned a primary site server at each of the 3 main locations
> > > and an additional primary site server at headquarters that would act as the
> > > central site server. Each of the other 18 locations would be setup as
> > > secondary site servers with Proxy MP and DP. I'm wondering if this is
> > > overkill. I feel that 4 primary servers is a bit too much.
> > >
> > > I've read the SMS CPDG document, and used the capacity planner. Based on
> > > those documents I believe that just one Primary server at headquarters with
> > > secondary servers /Proxy MP/ and DP at each of the other 20 remote locations
> > > (including the 2 main regional locations) may be sufficient.

--
Kim Oppalfens
MVP SMS
Computacenter Belgium
.

Relevant Pages

  • RE: How to remove an orphaned Primary Child Site from his Parent Stie
    ... Are the adresses on the parent site deleted. ... SMS 2003 Secondary Sites - Cleanly Removing SMS ... Perhaps a server is being decommissioned or rebuilt, ... where you need to remove the SMS secondary site installation from your server ...
    (microsoft.public.sms.admin)
  • Re: Site Code Not Discovered.
    ... There is a Troubleshooting Management Points whitepaper on the SMS website ... installing a management point. ... DHCP Setup - are the clients looking at a specific DHCP Server ...
    (microsoft.public.sms.admin)
  • Re: Network discovery Search to Subnet
    ... QIP (another system DHCP - not compatoble with SMS). ... I want to use the network discovery search by subnets but it doesn't work. ... Windows Server System MVP - SMS ... 360 secondary site 2003 sp2 ...
    (microsoft.public.sms.admin)
  • Re: Why does Microsoft call SMS a server
    ... Windows Enterprise Management Division User Assistance ... Check out the SMS Technical FAQ: ... SMS is really a server application that should be implemented and managed ... by a operations team, a operations team with different branches, clients ...
    (microsoft.public.sms.misc)
  • Re: NLB MPs & SMS DB
    ... Q. Can SMS 2003 be installed in a cluster server? ... Cluster Service" section in Chapter 10 of the Systems Management Server 2003 ...
    (microsoft.public.sms.admin)
Loading