Link to home
Start Free TrialLog in
Avatar of smith1974
smith1974

asked on

X500/LegacyExchangeDN queries

Hi

Some questions on X.500/LegacyExchangeDN's in an Exchange 2007 environment. Most of our mailboxes are manually created by Helpdesk, but we also have some that are automatically created (special mailboxes such as sales@domain.com etc).

1. If I check a user's mailbox properties within EMC, I can see that they have X500 addresses. Are these the same as a LegacyExchangeDN (LED) address?

2. Our special mailboxes don't have X500 addresses, does this mean they don't have LED addresses? If so, how does Exchange route the internal mail?

3. Is the LED a property of the AD account or the Exchange mailbox? That is, if Domain\Smith has an LED of X, and I then connect that AD account to another mailbox that has an LED of Y, what LED does Smith user have?

ASKER CERTIFIED SOLUTION
Avatar of Amit
Amit
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of smith1974
smith1974

ASKER

Thanks, do you know how Exchange creates the LED value? Is the CN part of it based on fields such as First Name, Last Name, etc or is it randomly created?
Apart from above article. Outlook store LED value under outlook.nk2 file. This way Outlook sends the email. If there are any issue like mailbox move corrupt issue. Where you might end up creating a new mailbox for old user. This LED value changes automatically to new one. But Outlook still stores the old value at the client end due to which users who are sending emails will get the bounce back message. There are three options to fix this issue.

1) Ask  user to select from GAL.
2) Delete outlook.nk2 file so it can be recreated.
Both above option are good for small env, but for big env it will be difficult to tell this to every user.

In that case Exchange admin can add the X500 with old LED value for corrupted user. This way bounce back message issue will be resolved.

Hope this clears the issue.