|
jbland -> ConfigMan Deployment questions (6/18/2008 3:30:48 PM)
|
I want to deploy Configuration Manager to our enterprise and need some advice on a couple of points i am trying to sell:
we have one forest, two domains
parent domain is out of state
child domain is local to me
SMS 2003 has been functional for four years only at the child domain - the parent domain now wants on board
parent domain has 700 clients
child domain has 200 clients
between domains there is a two-way transitive trust
I would like to set up two primary site servers, one for the parent and set this one up first so that it defaults to central
site; and one for the child.
I do not want the child site server to be a secondary site server because the stuff we push out to the child domain may or may
not be the same thing as what we push out to the parent domain.
I am the designated ConfigMan Admin, and would like the two servers to be physically located at the child site, for ease of
administration and for my ability to touch the machines if i have to. also, our server room power-wise and HVAC-wise is a better environment than the parent domain because we have less load.
Plus, I don't want to move.
Communication between sites is over a WAN through a 45MB pipe.
With 700 clients at the parent site, does anyone see any significant issues WAN-wise if staggered deployments are made to these
700 clients from the primary site server physically located at the child site.
since we are such small potatoes, the second question is - should there just be one site server for both domains? again, the site server would ideally be physically located at the child site.
is the physical location of the site servers residing at the child site an issue other than possible WAN related things?
thanks for the help.
|
|
|
|
