Solved

Cross-Forest Migration NDR Message

Posted on 2013-12-12
1
819 Views
Last Modified: 2013-12-12
Working towards a cross-forest migration from sub.source.com and dest.com.  Both domains have the same primary e-mail address domain currently, both are on Exchange 2010 (sub.source.com no updates, dest.com 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 sub.source.com to dest.com.  After the move

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

The X500 address moves over properly along with other necessary Exchange attributes to dest.com.  I believe due to the way Exchange internally routes e-mail it's get's hung up replying to the internal address of the sub.source.com 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 dest.com, 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?
0
Comment
Question by:maxtexgr
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 

Accepted Solution

by:
maxtexgr earned 0 total points
ID: 39715753
http://therealshrimp.blogspot.com/2010/01/cross-forest-mailbox-migration.html

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.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Group policies can be applied selectively to specific devices with the help of groups. Utilising this, it is possible to phase-in group policies, over a period of time, by randomly adding non-members user or computers at a set interval, to a group f…
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

689 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question