Problem with users alias after 2003 to 2007 migration

[astaylor]

After migrating a user to our Exchange 2007 server from 2003 using the move-mailbox command I have noticed that the users display name in Outlook 2003 shows up like this:

John Doe <migstubyhk0-f14-304-servername>

I have no problem sending an email to this user. It is just a bit odd. I have checked within the users properties and the display name and alias settings are correct.

Also, it's not just me. It shows up like this for any user within Outlook. I am not using Cached Mode.

We are updated to SP1 Update Rollup 8

Anybody seen this and know how to correct?

-drew

MCSA 2003: Messaging

 

[SilviaS]

What happens when you create a new user, can you have a look at the users attributes can confirm if this is set anywhere?

 

[astaylor]

Well the weird thing is that this is only happening for about half of the migrated users. The other half are OK. I have looked through the users properties and cannot see a difference from one user to the next. The display name and alias settings for the users with this wierd issue are all set correctly.

Any idea where it is pulling this string of characters from?

-drew

MCSA 2003: Messaging

 

[SilviaS]

are you using AD 03 or 08?
Also please check the user properties using ADSI edit.

 

[astaylor]

I was able to figure out the problem using ADSIedit. There is a property called legacyExchangeDN used by older Exchange versions and also is closely tied in with Outlook versions 2003 and lower.

From what i gather, when migrating to 2007 from 2003 the accounts are given a temporary alias that is the weird character string that i posted above. Now why it stayed for some users and not others i cannot explain, but at least i know where to correct it.

Thanks SilviaS for pointing me in the right direction to narrow down this issue.

-drew

MCSA 2003: Messaging

 

[Zelandakh]

Try:

Set-Mailbox -id AliasName -ApplyMandatoryProperties

which should fix this.

 

[astaylor]

I ran this command but it comes back with "ran successfully but no settings have been changed". Still seeing the same weird character string afterwards. A powershell command to fix this would be awesome.

-drew

MCSA 2003: Messaging

 

[Zelandakh]

In Ex 2007 Mgmt Console, check the Exchange alias for the user. Does it have a space?

 

[astaylor]

In the Mgmt console the alias shows up correctly and there are no spaces. Everyone sees the weird character string in Outlook in the Autocomplete list. It looks like it is pulling it from this legacyExchangeDN attribute. On our old Exchange server this attribute matches the alias.

-drew

MCSA 2003: Messaging

 

[SilviaS]

Hi again
Have a look at this link

http://www.msexchange.org/tutorials/Understanding-LegacyExchangeDN.html

The Question I ask is that with 2007 exchange is there a need to have the legacyEchangeDN attribute set.

Can you remove it from a couple of test users and review the impact?

 

[SilviaS]

This makes more sense
Can you rename the nk2 file in the users outlook profile so it rebuild and see if you still have issues.

http://mostlyexchange.blogspot.com/2007/08/exchange-2007-legacyexchangedn-and-mail.html

 

[SilviaS]

I would leave the legacyDN or if you can get the correct setting for this then updates the users that have incorrect legacydn attributes.

 

[astaylor]

Yeah i think it best to leave the setting. I am not very good with powershell and i'm still trying to figure out what exactly the script in the link above does. I have tried messing around with the NK2 and that still doenst seem to fix the problem.

-drew

MCSA 2003: Messaging

 

[Zelandakh]

The NK2 wouldn't fix the issue, it is just a nickname file. Deleting it is the quickest way to test!

 

[Zelandakh]

Essentially, the script will set the X500 address of the recipient to the LegacyExchangeDN if it isn't already set.

 

[SilviaS]

Have you tried to manually set the legacyDN to make sure it resolved the issue?