Hi, Can any one share details on the benefits of Single forest domain structure over multiple child domains, along with exchange 2010. In case child domain is created how will exchange server be placed. 1. Parent domain - Exchange is placed - will the child domain users achieve sso. 2. Child domain - Exchange in each domain. (is it recommended/feasible)Regards, Kiran B.

Personally I wouldnt put this down as an Exchange question. Any mailbox server throughout a forest, and any trusted forest, can house a mailbox for any server in any domain so there are zero benefits. Maybe you want to control who is managing servers throughout a given geo (APAC, EMEA, Americas etc) but even then security is across the forest not a domain. Elevation isnt rocket science these days. Does the organization lend itself to having an environment where multiple domains are required? (regulatory, local corporate politics, empire building morons etc.). If thats the case then theres going to be a knock-on effect that determines where the mailbox servers end up sitting. Ideally Id have everything centralised under a competent infrastructure team who can back each other up rather than have some guy out in Ulan Bator who demands his own domain because of some barely credible reason. Obviously your mileage will vary and local requirements outside of anything Exchange throws at you. Just remember that there have to be Exchange Org Admins that have rights over everything so no Exchange server is ever an island in a major global enterprise. "Kiran Arunkumar Babu" wrote in message news:9452d59f-283b-4ab7-8a33-eadb3c47d610... Hi, Can any one share details on the benefits of Single forest domain structure over multiple child domains, along with exchange 2010. In case child domain is created how will exchange server be placed. 1. Parent domain - Exchange is placed - will the child domain users achieve sso. 2. Child domain - Exchange in each domain. (is it recommended/feasible) Regards, Kiran B. Mark Arnold, Exchange MVP.

>>In case child domain is created how will exchange server be placed? I did such a test in my lab environment these days. You just need to pay attention to below options: 1. Add the administrator of child domain into Schema Admins and Enterprise Admins, then prepare domain for the child domain. 2. Force AD replication and wait until the permission replication finished. You need to wait for a night. 3. Then install Exchange 2010 in the child domain as normal.

Hi, Can any one share details on the benefits of Single forest domain structure over multiple child domains, along with exchange 2010. In case child domain is created how will exchange server be placed. 1. Parent domain - Exchange is placed - will the child domain users achieve sso. 2. Child domain - Exchange in each domain. (is it recommended/feasible) Regards, Kiran B. 1. There really isnt a huge benefit for having multiple domains in a single forest for Exch. If you have multiple forest (resource-forest model) then yes, But this ismore complex to deploy and manage. 2. Only benefit for a multiple child domains is to seperate high level priveldge accounts such as schema access account from the normal users. The downside is that it will mean an increase in costs as you will need more infratsicture for DC/GC and operational costs. 3. Unless you have a secuirty requirement go for a single forest/domain model.Sukh

Hi, Can any one share details on the benefits of Single forest domain structure over multiple child domains, along with exchange 2010. In case child domain is created how will exchange server be placed. 1. Parent domain - Exchange is placed - will the child domain users achieve sso. 2. Child domain - Exchange in each domain. (is it recommended/feasible) Regards, Kiran B. Like Mark sez, Domains are weak security boundaries- unless this is 1997 and you still believe the old Microsoft documentation. If I was building a new forest, it would be one domain.