legacyExchangeDN

Bentley · Joined: 06 Aug 2007 Posts: 1

All in the same forest, I have one win2k domain that was upgraded from NT and
I have 2 win2k3 domains that were upgraded from NT to 2000 to 2003.

In the 2000 domain, I discovered that user accounts that have been in the
system from the NT days have a legacyExchangeDN path of:

/o=organization/ou=mail/cn=recipient/cn=everyone/cn=mailboxname

Users who have been added to the system in the past few years and were not
NT accounts have this path:

/o=organization/ou=mail/cn=recipient/cn=mailboxname

When I tried to activate one of the latter users via a Blackberry server,
the account/device would not activate and then I noticed the difference in
the mailbox path. Not sure if that is causing the activation problem, but
the big question is, why are the newer accounts different and is it hurting
anything.

I realize that starting with Win2k3, there was no more Everyone group per
se, but this domain is still W2k.

I plan to upgrade this domain within 6 months and I do not want to run into
any issues with this.

Thanks

Archived from group: microsoft>public>exchange2000>active>directory>integration

Leif Pedersen [MVP] · Joined: 05 Aug 2007 Posts: 193

Hi,

The difference in legacyexchangedn should not cause any issues.

Leif

"Bentley" wrote in message @microsoft.com...
> All in the same forest, I have one win2k domain that was upgraded from NT
> and
> I have 2 win2k3 domains that were upgraded from NT to 2000 to 2003.
>
> In the 2000 domain, I discovered that user accounts that have been in the
> system from the NT days have a legacyExchangeDN path of:
>
> /o=organization/ou=mail/cn=recipient/cn=everyone/cn=mailboxname
>
> Users who have been added to the system in the past few years and were not
> NT accounts have this path:
>
> /o=organization/ou=mail/cn=recipient/cn=mailboxname
>
> When I tried to activate one of the latter users via a Blackberry server,
> the account/device would not activate and then I noticed the difference in
> the mailbox path. Not sure if that is causing the activation problem, but
> the big question is, why are the newer accounts different and is it
> hurting
> anything.
>
> I realize that starting with Win2k3, there was no more Everyone group per
> se, but this domain is still W2k.
>
> I plan to upgrade this domain within 6 months and I do not want to run
> into
> any issues with this.
>
> Thanks
>
>
>
>
>
>

legacyExchangeDN When a users mail nickname is modified (for marriage or whatever) does the LEDN need to be modified as well or is it not important whether it matches the I have read various information on the web and some say it doesn't matter, while othe

Disable display of the legacyExchangeDN Value Hi, we've migrated from Exchange 5.5 to Exchange 2003 and now the standard policy displays the when an user writing an e-mail in Outlook. Is there a way to remove this display within this policy? (exchange recipient policy)

legacyExchangeDN for sending-as a hidden public folder? I would like to be able send mail as a hidden public folder. We have exchange 2003/AD2003. there seem to be only one workaround which is to create a contact in my local outlook with the same address as a public folder. The only other potential solution th

Out of office notification Hi, I have exchange 2003 in my When user configure out of office assistant option in outlook and whenver any other user sends email to him a sender will get out of office notification only once that is first time. After that he will not ge

unkown specific address bit error - I havent seen this one b here is what I see in event log, I see several of them and I have not seen this before. just what does this mean? I googled it and didnt really come up with anything as far as the unkown access bit error. Event Type: Failure Audit Event Source: Se