Hi,Just a few quick questions about this...Firstly does Outlook 2007 still use the NK2 file with the legacyExchangeDN as the end target? I seem to have noticed that in Outlook 2003 auto complete the alias would be shownin the to bar as<ALIAS> but in Outlook 2007 it seems to show <email address>??Secondly I am trying to work out this article:http://www.amset.info/exchange/usernamechange.aspIt mentions renaming the user alias to change the value in the Auto complete, and if you do this then users cannot reply to old mail etc, but just changing the alias on my test account, only amends the mailNickname attribute and it does not touch the legacyExchangeDN, so I do not understand if it all ultimately resolves to the legacyExchangeDN why this fails?Just trying to work this all out?!

On Tue, 27-Oct-09 08:45:53 GMT, UselessUser wrote:>Hi,Just a few quick questions about this...Firstly does Outlook 2007 still use the NK2 file with the legacyExchangeDN as the end target? All version of Outlook eventually use the legacyExchangeDN to send themessage if the recipient is on an Exchange server in the sameorganization as the sender's mailbox -- and if the connection is usingRPC. If you're asking about a file format that Outlook uses you'd geta better answer, I think, in an Outlook group.2003 auto complete the alias would be shown in the to bar as but in Outlook 2007 it seems to show ??Secondly I am trying to work out this article:http://www.amset.info/exchange/usernamechange.aspIt mentions renaming the user alias to change the value in the Auto complete, and if you do this then users cannot reply to old mail etc, The email in the mailbox (assuming it came from a mailbox in the sameExchange organization) uses an O/R address that's the sender's (andother recipient's) legacyExchangeDN name. Changing the value of themailNickname property on the user doesn't alter the value of theuser's legacyExchangeDN -- so email will still be delivered to thecorrect recipients.>but just changing the alias on my test account, only amends the mailNickname attribute and it does not touch the legacyExchangeDN, This is a "good thing". Changing the legacyExchangeDN value can causemany problems (not just undeliverable mail).y resolves to the legacyExchangeDN why this fails?It doesn't.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP