?
Solved

X500/LegacyExchangeDN queries

Posted on 2011-02-13
4
Medium Priority
?
922 Views
Last Modified: 2012-05-11
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?

0
Comment
Question by:smith1974
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 44

Accepted Solution

by:
Amit earned 2000 total points
ID: 34883478
By Default all user have LED value. You can check it using ADSIEDIT.MSC tool. It seems someone might manually added the X500 connector for email bounce back issue. As Outlook stores the LED value.
0
 

Author Comment

by:smith1974
ID: 34901737
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?
0
 
LVL 44

Expert Comment

by:Amit
ID: 34903682
0
 
LVL 44

Expert Comment

by:Amit
ID: 34903703
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.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to install and use the NTBackup utility that comes with Windows Server.
I don't pretend to be an expert at this, but I have found a few things that are useful. I hope that sharing them here will help others, so they will not have to face some rather hard choices. Since I felt this to be a topic of enough importance and…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Suggested Courses

764 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question