considerscs
asked on
Global Contact Issue After 2003 to 2010 Exchange Migration
We upgraded from Exchange 2003 to Exchange 2010. All users and mailboxes were migrated, but 1 mailbox needed to be recreated, as it never sync'd. The mailbox was recreated but the AD user was not recreated. The issue we are having is that when staff try to send an e-mail to this mailbox (by selecting it in their global contact list, not from cached) they get a bounce back. I believe they are getting this bounce back because the global contact for this mailbox is pointing to the old mailbox. The mailbox can still receive email if you type in the full address, but not if you select the global contact.
Any suggestions?
Any suggestions?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
"
In my case, due to our upgrade to Exchange 2007, the user’s legacyExchangeDN value had changed from this on the old mailbox (which had been created prior to the Exchange 2007 upgrade):
/o=Example/ou=USA/cn=Recip ients/cn=j user
To this on the new mailbox:
/o=Example/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recip ients/cn=j user
"
On all of my mailboxes, they already have an x.400 address of:
"
C=us;A= ;P=Example;O=Exchange;S=La stName;G=F irstName;
"
^ This seems to be what the article found to put in for the x.500 address. I tried that and did not have success. When I ran Exchange Management Shell to find the current X.500 address of this user, i got this, which is exactly what the article states:
"
/o=Example/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recip ients/cn=: FirstName
"
I am trying to get a hex editor and go through that part of the article to double check the old X.500 address. The Microsoft Exchange Server MAPI Editor seemed to need a lot of additional setup for it to work correctly.
In my case, due to our upgrade to Exchange 2007, the user’s legacyExchangeDN value had changed from this on the old mailbox (which had been created prior to the Exchange 2007 upgrade):
/o=Example/ou=USA/cn=Recip
To this on the new mailbox:
/o=Example/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recip
"
On all of my mailboxes, they already have an x.400 address of:
"
C=us;A= ;P=Example;O=Exchange;S=La
"
^ This seems to be what the article found to put in for the x.500 address. I tried that and did not have success. When I ran Exchange Management Shell to find the current X.500 address of this user, i got this, which is exactly what the article states:
"
/o=Example/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recip
"
I am trying to get a hex editor and go through that part of the article to double check the old X.500 address. The Microsoft Exchange Server MAPI Editor seemed to need a lot of additional setup for it to work correctly.
just create x500 and add this /o=Example/ou=USA/cn=Recip ients/cn=j user
ASKER
Okay I added that, and still received a bounce back. Is there a specific amount of time needed to let the change populate?
Here is the bounce back:
"
Diagnostic information for administrators:
Generating server: SERVERNAME.Example.local
IMCEAEX-_O=Example_OU=Firs t+20admini strative+2 0group_cn= Recipients _cn=FLastN ame@exampl e.org
#550 5.1.1 RESOLVER.ADR.ExRecipNotFou nd; not found ##
"
Here is the bounce back:
"
Diagnostic information for administrators:
Generating server: SERVERNAME.Example.local
IMCEAEX-_O=Example_OU=Firs
#550 5.1.1 RESOLVER.ADR.ExRecipNotFou
"
So the X500 you need to add based on the above is:
/O=Example/OU=First administrative group/cn=Recipients/cn=FLa stName
/O=Example/OU=First administrative group/cn=Recipients/cn=FLa
ASKER
That fixed it. Thank you very much.
Hmmm, you could of given some "Assist" points, oh well...
ASKER
I'm sorry, i overlooked your username. Sorry about that.
No problem. ;-)
http://www.simple-talk.com/sysadmin/exchange/exchange-e-mail-addresses-and-the-outlook-address-cache/
http://msexchangeguru.com/2012/03/15/x500/