Internal NDR after Exchange migration to Office 365

Hi, I just migrated our old Exchange 2003 server to Office 365.  Everything is running well, except we are getting NDR's when sending internal email.  Does this have something to do with how the old Exchange server sent internal mail?
IgniteITNSAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
BlueComputeConnect With a Mentor Commented:
So it looks like this is an Active Directory issue.  When a user selects a coworker from the Contacts list, the email will go through and autocomplete will fix the email address.  But you have to send them an initial email first.

Close.  For internal users outlook uses the LegacyExchangeDN address (also known as the x500 address).  The cached autocomplete entries reference the x500 address, which the new external exchange server can't resolve to a mailbox.  If the user sends an email to the smtp address (someone@somewhere.com) then that entry will be added to the *.NK2 file, so future emails will be sent correctly.

There are two ways of resolving this, one more elegant than the other:
1) Train the users to type the address in once for each contact (the first time they send to them), or edit the autocomplete entry using something like Nirsofts NK2edit.

2) Determine/extract the x500 attribute from your AD using ADSIedit or similar and have these LegacyExchangeDNs added as additional addresses to the mailboxes on O365.  This blog documents the process: http://joystickjunkie.blogspot.co.uk/2012/07/office365-migrations-and.html

There seems to be a lot more good gen out there if you google 'office 365 legacyexchangedn' so hopefully that'll see you right.
0
 
IgniteITNSAuthor Commented:
So it looks like this is an Active Directory issue.  When a user selects a coworker from the Contacts list, the email will go through and autocomplete will fix the email address.  But you have to send them an initial email first.
0
 
ArneLoviusCommented:
to expand on IgniteITNS

if people are using saved autocomplete entries, these will fail as although the display name will remain the same, the back end data has changed.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
what the NDR code?
0
 
ArneLoviusCommented:
@BlueCompute beautifully written
0
 
BlueComputeCommented:
Thanks ArneLovius - I'm thinking of turning some of my answers here into blog posts or a pewrsonal KB so I'm trying to make them as complete and clear as possible without going overboard.
0
 
IgniteITNSAuthor Commented:
I've requested that this question be deleted for the following reason:

was typed in by ex employee,
0
 
ArneLoviusCommented:
You seem to be saying that multiple users have access to a single account.

http://www.experts-exchange.com/terms.jsp

If you register for Services, these Services are for the registered user ONLY and may not be shared or features transferred to others
0
 
IgniteITNSAuthor Commented:
No what I'm saying is that the IT guy I paid who was using this account was let go. I am now doing his job.   Only one user guys....
0
 
ArneLoviusCommented:
I am 100% sure that the answer provided by myself and exceptionally well described by BlueCompute is correct.

I would split the points 50/50 across posts 38779740 and 38780856


The issue of an account being " transferred to others" ...
0
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.