Cross-Forest Migration NDR Message

Working towards a cross-forest migration from and  Both domains have the same primary e-mail address domain currently, both are on Exchange 2010 ( no updates, SP3).  The migration is being done in 3 sections by location over a 2-3 week period, ~50 users, ~80 users, ~200 users.

The process we're following via custom powershell script is prepare-mailbox script, ADMT users over including passwords though excluding exchange attributes, and then move mailbox from to  After the move

- Can login with previous password
- All data is moved
- New messages both ways work
- Old e-mail replies from work to
- Old e-mail replies from to don't work.

The X500 address moves over properly along with other necessary Exchange attributes to  I believe due to the way Exchange internally routes e-mail it's get's hung up replying to the internal address of the users as both sides are the same e-mail domain name.  It sounds like it's looking at the hub transport, tries to find the old user based on internal address, errors out as that users doesn't exist in, and NDRs.

Any tips on how to get past this?  Temporary contacts or perhaps there's something I'm missing?

Thank you for your help and this is pre-migration so fortunately testing has shown the issue beforehand.  I am aware the GAL won't be the same and free/busy will have some problems.  Anything else that you guys can foresee as issues?
Who is Participating?
maxtexgrConnect With a Mentor Author Commented:

Creating a target domain contact with the sources legacyexchangedn as the x500 address fixes it.  So for any non-migrated users a contact will need to be made.  Simple enough.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.