Hi,I recently created a child domain, let's call it child.company.local as a delegation to our root domain, company.local according to these instructions:http://support.microsoft.com/kb/255248http://technet.microsoft.com/en-us/library/cc780951.aspxhttp://technet.microsoft.com/en-us/library/cc787706.aspxI am now going through the V3MigGuide from page 225 onwards that describes how to migrate objects between domains in the same forest, which I am doing.I ran through the following test scenario: 1. Create a test user in the source domain. Include this test user with your migrations. 2. Join that user to the appropriate global groups to enable resource access. 3. Log on to the source domain as the test user, and verify that you can access resources as appropriate. 4. After you migrate the user account, translate the user profile, and migrate the workstation of the user, log on to the target domain as the test user, and verify that the user has retained all necessary access and functionality. For example, you might test to verify that: The user can log on successfully. The user has access to all appropriate resources, such as file and print shares; access to services such as messaging; and access to line-of-business applications. It is especially important to test access to internally developed applications that access database servers. The user profile was successfully translated, and the user retains desktop settings, desktop appearance, shortcuts, and access to the My Documents folder. Also, verify that applications appear in and start from the Start menu.With my test account I can logon ok, access to all appropriate resources, such as file and print shares etc. But the problem is I cannot access any email while logged onto the child domain - it says 'exchange server is not available'. Funny thing is when I initially configured outlook to connect to the exchange server, which is located on the root company.local domain, it found my username because it highlighted it.So what step am I missing here?? Can someone shed some light on the matter for me please - why can I not access the email server on the root domain while logged onto the child domain? Is there something in exchange recipient policies I need to configure, or something else?I have awindows/exchange/outlook 2003 environment which is full 2003 functional level.btw, when I created the child domain, I did not run any domain prep on it because it didn't say in the MS instructions in the links above. Should I have? And if so, can I still do it now and will I need to do it with server 2003 CD or Exchange 2003 domain prep, or both?This is kind of urgent...Thanks,Taz

Firstly, I am confused with the concept of migrating the user accounts from a newly created child domain to parent domain. As far as exchange is concerned there is no need to do so as far as you have some other requirement for doing so. Though the document does not state anywhere you should run the domainprep in child domain as well. Exchange wont understand anything that does not allow exchange domain servers and other security groups to read information from or write to AD objects. You dont neeed to run either of AD prepration switches only when you are working with a resource forest scenario. The other forest than Exchange doesn't need to be domain prepared. I MMilind Naphade | MCTS:M | http://www.msexchangegeek.com

As my post states, I am migrating users from the root domainTO the newly created child domain (same forest), not the other way around :)Anyway, for some reason I am now able to connect to the exchange server when logged onto the child domain after a while, maybe it was a replication thing.AsI said, the doc doesn't state anything about domainprep on exchange, but I heard that this should be done. Anyway since then I have gone and done the domainprep on the child DC.There is also an article that explains how to Creating Exchange Recipient Service instances for remote domains (http://support.microsoft.com/kb/275294/ ). Is this step even necessary to add the new child domain in exchange RUS? I heard this needs to be done in order to allow exchange to access the mailbox objects in the child domain..?But when I try to do this I get a RPC server not available error. This seems to point to dns resolution, but I can do an nslookup from machines in both the root domain and child domain. The child domain was installed using a delegation to the root domain. Please clarify.Thanks,Taz

Taz,For the rest of the questions, Yes! you do need to create RUS for child domains as well. Every child domain should have a corresponding domain RUS so that Exchange can have a definite path to search for recipients in that domain. As far as RPC server unavailable issue is concerned, it may be because of number of reasons like DNS resolution till AD replication and permissions. Hopefully, you getit fixed quickly.I did read your post the other way, by the ways. Thanks for setting me up straight ;)MMilind Naphade | MCTS:M | http://www.msexchangegeek.com