Hi,We're currently testing Exchange 2007 on Server 2008 in our concept environment.After some initial issues with name resolution we're doing ok however it doesn't seem straightforward to arrange the user accounts as we would like.When we come to deploy we want to be able to have a root domain (company.local)with all our user accounts in with the exchange servers and groups in a child domain (mail.company.local).However, when I go to create a new user via the Exchange new user GUI I'm only shown OU's within the child domain not the root. Both domain have had setup/preparead run and everything else is looking rosie.

with a Empty forest root (EFR) you will have to prepare the schema and the forest.In the child domain you will need to prepare AD in the child.The Exchange security groups will be located at the EFR for the entire exchange organization.When you deploy exchange it will be done at the child level on servers in the child domain. users when created will be created for that child domain. You may need to change your scope when creating user accounts depending on where you have your Exchange Servers deployed.So, that leads me to the question, where are your Exchange Servers deployed?SF - MCITP:EMA, MCTS

Hi Bardapony, thanks for the reply.We aren't deploying an empty root, we are deploying a root for user accounts. All services, such as Exchange, are then being placed within child domains.All the exchange servers are deployed within the child (mail.company.local) and all user accounts would ideally be located in the root (company.local) with mailboxes on the servers in the child domain (mail.company.local). I hope this is making sense.So when I run the account creation tool in exchange console and I select new account I'm only shown locations in the mail.comany.local domain.Prepareschema was run in the root and preparead was run in both child and root domain during the exchange installation.

Found some usefull pointers here:http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/e7d41fcf-eb7e-4762-ad7a-f497201e7fa1/Currently looking into the forementioned Hub transport configs

Yep, this worked. Right click Recipient configuration in the root of the Exchange console, select modify recipient scope and then select use entire forest.