giving users in child domains exchange accounts from parent domain

[deeno]

Our company has been running in a single domain. We recently added a remote office and configured a child domain. Our Exchange servers are located in our parent domain.

Does anyone know what additional steps would need to take place on the child domain in order to allow an account from the child domain to be able to become exchange enabled?

We have installed ESM on the remote domain controller and I’m able to create the mailbox from the remote site but the mailboxes don’t work.

Any ideas?

Thanks...

 

[BenChristian]

You need to run domainprep in the child domain. Once you have run domainprep you will be able to mail enable/mailbox enable the user accounts in that domain.

Ben Christian
MCSE, MCSA:Messaging

http://www.benchristian.com

 

[deeno]

Ben,

Thanks for the tip... Domainprep has been run and I've also manually created the recipient update policy on for the child domain.

Weird, no errors, just doesn't work.

 

[TweakMYbox]

What are the symptoms? Are they able to login to a MAPI profile?

Mike

http://tweekmybox.com

 

[deeno]

users in the remote domain, after being given exchange accounts, cannot connect to their mailbox through MAPI clients or through any other client (web based or whatever). Under the email accounts tab in AD, there is no information about the SMTP address or x400 address...

 

[deeno]

ok... the problem with the RUS updating is fixed... was a problem resolving the short names of the remote domain controllers from the exchange servers... here is the article...

http://support.microsoft.com/kb/275294

Now the issue is that users still cannot connect to their mailboxes, but at this point it seems to be a permissions issue for the remote account mailboxes.

 

[BenChristian]

If you were having name resolution problems between Exchange server and the DC in the other domain, you may also have name resolution problems between the clients in that domain and the Exchange server. Check to make sure that the clients can properly resolve the name of the Exchange server.

How is DNS configured for your domains? It sounds like your DNS servers are only resolving names for their own domain.

Ben Christian
MCSE, MCSA:Messaging

http://www.benchristian.com

 

[deeno]

Ben-

Thanks for the advice... it turned out that after my last post it was working, it was just taking a considerable time for the account information to replicate. So it seems that all along it was the issue with our exchange servers at the parent site not being able to resolve the short names of the remote domain controllers.

Aside from that, DNS was correctly configured all along at both sites.

Thanks for the tips... if anyone else has this issue... as it has been pointed out, be sure that domainprep is installed and make sure that the short names can be resolved for machines on both sides from either side...