It will have an X500 address. Always. Exchange internally uses X500 (even in vNext!) for address routing and translation.
legacyExchangeDN (lEDN) is the AD attribute. You cannot duplicate lEDN in a forest. If you force it, you break Exchange. I haven't read down through this entire thread (today was a long day), but I had to respond to that one thing. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ben Scott Sent: Monday, January 19, 2015 3:32 PM To: [email protected] Subject: Re: [Exchange] Replacing an account, Outlook autocomplete is stubborn On Mon, Jan 19, 2015 at 2:25 PM, Mike Tavares <[email protected]> wrote: > I believe the cached entry is using the X:500 address which is why it > is still finding the old mailbox instead of the new one. That was my thought, too, which is why I tried rejiggering the X.400/X.500 addresses. The JSMITH mailbox does not even *have* an X.400 address at this point. But Outlook is still finding the JSMITH mailbox, somehow. To provide more detail on what we did: The old JSMITH mailbox would have had an X.400 address like: C=us;A= ;P=ExampleCorp;O=Exchange;S=Smith;G=John; I coped that to my notes, and then removed it from the JSMITH mailbox. That left the JSMITH mailbox with no X.400 addresses at all. Then, on the newly-created JSMITH2 mailbox, the default X.400 address was: C=us;A= ;P=ExampleCorp;O=Exchange;S=Smith2;G=John; So I added a custom address, type "X400", and pasted in: C=us;A= ;P=ExampleCorp;O=Exchange;S=Smith;G=John; Then I set that as primary/reply. So now JSMITH2 has two X.400 addresses, one of which was copied from JSMITH. For good measure, I forced an update of the OAB, but the problem happens even if I'm running Outlook in online mode. I also tried nuking my Outlook/MAPI profile and local data files. Same behavior with my autocomplete cache. -- Ben
