SMS 2003 Hierarchy Design
- From: "Kane" <Kane@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 12 Jul 2005 12:54:04 -0700
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.
Any suggestions on this design? Is it necessary to have secondary sites
with proxy management points at each location, even if there are only 10
clients at the site?
.
- Follow-Ups:
- Re: SMS 2003 Hierarchy Design
- From: Kim Oppalfens
- Re: SMS 2003 Hierarchy Design
- Prev by Date: Re: SMS 2003 Client on Server
- Next by Date: SMS install
- Previous by thread: Running SMS 2003 SP1 on a vmware server in a production environmen
- Next by thread: Re: SMS 2003 Hierarchy Design
- Index(es):
Relevant Pages
|
