Currently we have the following setup: Forest A Domain UK 1 SCCM 2007 SP2 R2 Primary/Central Server 10 Secondary Site Servers Forest B Domain DE 1 SCCM 2007 SP2 R2 Central/Primary Site Server NLB Management Point No Secondary Site Servers but multiple Dist points Domain EU New domain created to manage both UK and DE new resources (Shared Group systems - mainly servers and not desktop/laptops) Objective: Both UK and DE teams need to start thinking about managing resources in EU domain collectively EU domain is already part of Forest B , the same Forest Domain DE is hosted, so DE dept are better placed to manage these resources 1 idea is to install a new primary server in EU domain and attach the existing DE Primary site server to report to this new central server I have a number of questions regarding this: Is it possible to install a new Central site which we will call EU1 after a primary server has been installed in the same forest? Can the UK Primary site server which sits in a different forest and domain be linked to the new Central site server which we will call EU1? If it is possible to link both UK1 and DE1 Site servers to EU1, how will this affect secondary servers in UK1 hierachy? The end goal is to manage the EU domain resources by both teams with minimal administartion and not have to manage multiple hierachies, but a central console ideally , settings in central site server do not have to replicate down to the two country site systems neccessarily as these are largely managed independently. I would appreciate your thoughts on this

See http://technet.microsoft.com/en-us/library/bb694003.aspx. #1: sure #2: yes #3/#4: objects created at the central site will be replicated down (collections, packages, DCM stuff, updates, etc). I am not sure what you mean by "settings". Client agent settings for example are site specific.

Thanks for that We would like to keep the country site settings independent from the each other such as : 1.Update deployments 2.Client agent settings 3.Software distributions If we create a collection or deployment management or a software distribution package at the top level central site will that replicate all the way down the hierachy even though we do not select dist points lower down the hierachy. I presume with the collections that they will be additional collections in the primary sites below, I think I have seen something like a padlock on the course?

Client agent settings will be defined at each site independently. Deployments and SW distributions created at the central site will be replicated down (resulting in locked objects on the child sites), but you are still able to create objects on each child site.

Thanks Torsten for your prompt feedback Is there any documentation you can point me to that will asist in me on this subject?