Are you running Exchange? This is very important, if so then you need to
watch out for what is called "Mangled Attributes."
An attribute becomes "mangled" if "Dup" or other unique characters are
added to the beginning of the conflicted attribute name so that objects and
attributes in the directory have unique names.
Active Directory forests are not vulnerable to mangled LDAPDisplayNames for
these attributes in the following cases: . If you run the Windows Server
2003 adprep /forestprep command in a forest that contains the Windows 2000
schema before you add the Exchange 2000 schema.
. If you install the Exchange 2000 schema in forest that was created
where a Windows Server 2003 domain controller was the first domain
controller in the forest.
. If you add Windows 2000 inetOrgPerson Kit to a forest that contains
the Windows 2000 schema, and then you install Exchange 2000 schema changes,
and then you run the Windows Server 2003 adprep /forestprep command.
. If you add Exchange 2000 schema to an existing Windows 2000 forest,
then run Exchange 2003 /forestprep before you run the Windows Server 2003
adprep /forestprep command.
Mangled attributes will occur in Windows 2000 in the following cases: . If
you add the Exchange 2000 versions of the labeledURI, the houseIdentifier,
and the secretary attributes to a Windows 2000 forest before you install the
Windows 2000 inetOrgPerson Kit.
. You add the Exchange 2000 versions of the labeledURI, the
houseIdentifier, and the secretary attributes to a Windows 2000 forest
before you run the Windows Server 2003 adprep /forestprep command without
first running the cleanup scripts.
The previous comes from the link below which will guide you through the 2000
to 2003 AD upgrade process.
http://support.microsoft.com/default.aspx?scid=kb;en-us;325379
--
Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
http://www.pbbergs.com/
This posting is provided "AS IS" with no warranties, and confers no rights.
