Hi, I always have some user need to rename AD Account during the promotion. However, I noticed after rename, Outlook 2K3 user still see the Old user account even after delete the autocomplete cache. Perhaps, can you share whether the example user A already change to B. The LegacyExchangeDN and ProxyAddresses should it be as below: How can we go about this? LegacyExchangeDN /o=abc/ou=Exchange Administrative Group/cn=Recipients/cn=A ProxyAddresses SMTP:B@abc.com X500:/o=abc/ou=Exchange Administrative Group/cn=Recipients/cn=A

Yes you can do that but you need to also change the legacyexchangedn. For example say his original legacyexchangedn was "A" /o=abc/ou=Exchange Administrative Group/cn=Recipients/cn=A Now you want to change it to B /o=abc/ou=Exchange Administrative Group/cn=Recipients/cn=B Then you also have to add the x500 to B's account. X500:/o=abc/ou=Exchange Administrative Group/cn=Recipients/cn=A James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

On Thu, 6 Sep 2012 14:10:38 +0000, Exchange2010 wrote: >I always have some user need to rename AD Account during the promotion. However, I noticed after rename, Outlook 2K3 user still see the Old user account even after delete the autocomplete cache. > >Perhaps, can you share whether the example user A already change to B. The LegacyExchangeDN and ProxyAddresses should it be as below: > >How can we go about this? > >LegacyExchangeDN /o=abc/ou=Exchange Administrative Group/cn=Recipients/cn=A I wouldn't recommend changing the legacyExchangeDN. Sure, you can add the original legacyExchangeDN as a X500 address on the mailbox's "E-mail addresses" tab, but there'll be other problems that arise after you do that (meeting requests, for example). There's really no good reason to change the LDN since it's not something a user has access to (or sees). >ProxyAddresses SMTP:B@abc.com X500:/o=abc/ou=Exchange Administrative Group/cn=Recipients/cn=A That'll work for e-mail, but other things may break because the proxyAddresses property isn't the legacyExchangeDN and a search for LDN "A" isn't going to find proxyAddress "A". --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

There is a lot existing suggestion like changing LegacyExchangeDN with ASDedit or LegacyDN.EXE. Am just want to find out the right way to doing this when rename an account. Is there anyway to solve Outlook 2k3 user that see the old user id A for this example. The deletion of cahce of auto-complete at Outlook and select from OAB seems given the old user id next to it A but not B. Is that really matter to update LegacyExchangeDN for this?

On Fri, 7 Sep 2012 00:28:49 +0000, Exchange2010 wrote: >There is a lot existing suggestion like changing LegacyExchangeDN with ASDedit or LegacyDN.EXE. Am just want to find out the right way to doing this when rename an account. As I said, the legacyExchangeDN isn't something a user sees. Leave it alone. There a lots of things you *can* change, but it doesn't mean you should. >Is there anyway to solve Outlook 2k3 user that see the old user id A for this example. The deletion of cahce of auto-complete at Outlook and select from OAB seems given the old user id next to it A but not B. Is that really matter to update LegacyExchangeDN for this? If you've renamed the account it doesn't mean the display name has changed. So what is it that you're changing -- name of the AD object, the samaccoutname, or the displayname, or is it something else? And how, if they're selecting the name from the OAB, would they arrive at the old name if they're looking for the new name? Using your example you've "renamed" 'A' to 'B'. How does the Outlook user find "A" while searching for "B"? If the Outlook is configured to NOT use the OAB are the results of the search different? Perhaps the OAB isn't being updated -- have you checked the application event log on the OAB server? Turn up logging on the "MSExchangeSA\OAL Generator" to "Highest" and force the OAB to regenerate, then check the event log. Or maybe the Outlook client isn't downloading the OAB. You can stop Outlook and remove the *.oab files from the machine and then start Outlook and force it to download the OAB. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Fri, 7 Sep 2012 02:31:49 +0000, Exchange2010 wrote: >The Outlook 2k3 already delete the existing cache on A, and during select from Address Book it shown B. > >However, subsequent new compose email afterward when type the name it appear user is A next to it. A and B in this case is a user id, the display name actually not changed. So all you changed was the sAMAccountName? How much of the name do they enter when "A" is offered as a suggestion? If they enter the complete name and then Ctrl+K is the name resolved correctly (i.e. is it underlined) and is the name "B"? Do you (and your users) expect the sAMAccountname and the alias to be identical? Outlook is going to use ambiguous name resolution to try and match as many AD objects as it can to whatever it finds in the set of recipients. Are you sure that these users don't have "A" in their Contacts folder? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

From the ADSIedit, can tell all the attribute is updated to B even the sAMAccountname. The Outlook 2k3 suggestion display corretly the full name, however the user id A that next to full name don't semms updated. At our case, user previously clerical may be the user ID is cl-A (A), after promotion to executive it changed to ex-A (B). Howerver, the outlook suggestion display username (A) but not username (B) althought it deleted the username (A) cache, and the updated username (B) show in the address book.

From the ADSIedit, can tell all the attribute is updated to B even the sAMAccountname. The Outlook 2k3 suggestion display corretly the full name, however the user id A that next to full name don't semms updated. At our case, user previously clerical may be the user ID is cl-A (A), after promotion to executive it changed to ex-A (B). Howerver, the outlook suggestion display username (A) but not username (B) althought it deleted the username (A) cache, and the updated username (B) show in the address book. Hi, Outlook 2003 will show the unique part of the LegacyExchangeDN in the Autocomplete cache and as far as I know, that can't be changed. In Outlook 2007/2010 that has been changed to show the SMTP Address instead.Martina Miskovic

From the ADSIedit, can tell all the attribute is updated to B even the sAMAccountname. The Outlook 2k3 suggestion display corretly the full name, however the user id A that next to full name don't semms updated. At our case, user previously clerical may be the user ID is cl-A (A), after promotion to executive it changed to ex-A (B). Howerver, the outlook suggestion display username (A) but not username (B) althought it deleted the username (A) cache, and the updated username (B) show in the address book. Hi, Outlook 2003 will show the unique part of the LegacyExchangeDN in the Autocomplete cache and as far as I know, that can't be changed. In Outlook 2007/2010 that has been changed to show the SMTP Address instead.Martina Miskovic

Agree, I haven't seen that for a while since on outlook 2k3 but recall having to change the legacyexchangedn a while back during account renames. Yes you don't typically want to change the legacyexchangedn it "may" cause issues in the future but haven't recalled where I was seriously bit by making changes, things RSG restores or other issues mentioned may bite you. If you decide to change just keep a record of the original legacyexchangedn. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Agree, I haven't seen that for a while since on outlook 2k3 but recall having to change the legacyexchangedn a while back during account renames. Yes you don't typically want to change the legacyexchangedn it "may" cause issues in the future but haven't recalled where I was seriously bit by making changes, things RSG restores or other issues mentioned may bite you. If you decide to change just keep a record of the original legacyexchangedn. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com