Exchange 2003 Migration - InetOrgPerson Problem

I recently installed my first Exch 2003(SP1) server on Windows Server
2003(SP1) in 2000 AD domain with an existing Exch 2000(SP3) server
(native mode). I ran forestprep and domainprep for Exch 2003 from the
Exch 2003 member server. I then ran forestprep and domainprep for
Server 2003 from the 2000 Schema Master DC, then from the 2000 PDC
Emulator DC. There were no errors. After that, I found the KB article
(314649) about the InetOrgPerson problem. I have not run the
InetOrgPersonfix script.

I did follow steps 1-5 under Scenario 3 from 314649, but nothing was
returned from the search for the LDAPDisplayName attributes:
Result <0>: (null)
Matched DNs:
Getting 0 entries:

My Exch 2000 server is still in the AD, and I have not moved the
mailboxes yet. I did create a test mailbox in 2000, and moved it to
2003. There were no errors or problems.

The question is, what do I do now?

Can I (should I) remove and re-install my new Exch 2003 server?

Can I (should I) re-run forestprep and domainprep for Server 2003 and
Exch 2003?

Is the InetOrgPerson problem going to prevent me from upgrading my DC's
from 2000 to 2003?

The article seems to indicate that I should have already had a problem
during Server 2003 forestprep.

TIA,
Chris

Ed
Fri Sep 23 15:06:34 CDT 2005

Answers are inline.

You should look into fixing the problem, if it exists, by following Scenario
3, or is there something about your environment that is different?
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"CMLlanes" <CMLlanes@discussions.microsoft.com> wrote in message
news:D05AEAD5-5833-4DFC-902D-61920AD8F98D@microsoft.com...
>I recently installed my first Exch 2003(SP1) server on Windows Server
> 2003(SP1) in 2000 AD domain with an existing Exch 2000(SP3) server
> (native mode). I ran forestprep and domainprep for Exch 2003 from the
> Exch 2003 member server. I then ran forestprep and domainprep for
> Server 2003 from the 2000 Schema Master DC, then from the 2000 PDC
> Emulator DC. There were no errors. After that, I found the KB article
> (314649) about the InetOrgPerson problem. I have not run the
> InetOrgPersonfix script.
>
> I did follow steps 1-5 under Scenario 3 from 314649, but nothing was
> returned from the search for the LDAPDisplayName attributes:
> Result <0>: (null)
> Matched DNs:
> Getting 0 entries:
>
> My Exch 2000 server is still in the AD, and I have not moved the
> mailboxes yet. I did create a test mailbox in 2000, and moved it to
> 2003. There were no errors or problems.
>
> The question is, what do I do now?
>
> Can I (should I) remove and re-install my new Exch 2003 server?
>
You can but should not.
>
> Can I (should I) re-run forestprep and domainprep for Server 2003 and
> Exch 2003?
>
You can but need not.
>
> Is the InetOrgPerson problem going to prevent me from upgrading my DC's
> from 2000 to 2003?
>
No.
>
> The article seems to indicate that I should have already had a problem
> during Server 2003 forestprep.
>
It says you "may" have a problem when installing Exchange 2000.
>
> TIA,
> Chris

CMLlanes
Sat Sep 24 18:13:02 CDT 2005

Ed,

Thank you for your answers. But I am still concerned about the lack of any
LDAPDispalyName attributes, mangled or not.

> I did follow steps 1-5 under Scenario 3 from 314649, but nothing was
> returned from the search for the LDAPDisplayName attributes:
> Result <0>: (null)
> Matched DNs:
> Getting 0 entries:

I am not able to complete Scenario 3, and correct the possibly mangled
attributes, if they are not there.

What is the function of these attributes?

Is this something that is going to cause me problems in the future?

Ed
Sun Sep 25 02:10:44 CDT 2005

The "mangled attributes" will really only cause problems with other LDAP
applications that expect them to be named a certain way.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"CMLlanes" <CMLlanes@discussions.microsoft.com> wrote in message
news:5452EF27-3474-4DCB-8B0E-2F3126AA4B77@microsoft.com...
> Ed,
>
> Thank you for your answers. But I am still concerned about the lack of
> any
> LDAPDispalyName attributes, mangled or not.
>
>> I did follow steps 1-5 under Scenario 3 from 314649, but nothing was
>> returned from the search for the LDAPDisplayName attributes:
>> Result <0>: (null)
>> Matched DNs:
>> Getting 0 entries:
>
> I am not able to complete Scenario 3, and correct the possibly mangled
> attributes, if they are not there.
>
> What is the function of these attributes?
>
> Is this something that is going to cause me problems in the future?