K
keven
This is an article from the MS-Web site on upgrading to
Windows 2003. If we ran forest prep and domain prep
before installing exchange 2000 does this apply?
Thanks Keven
Exchange 2000
If you've installed Exchange 2000 into the forest before
running AD Prep, you have to correct some mistakes that
were made in the Exchange 2000 schema extensions.
Specifically, both ADPrep and Exchange 2000 define
labledURI, houseIdentifier and secretary attributes, but
Exchange 2000 does not use the correct LDAP display names
(lDAPDisplayName) as defined in RFC 2798. If you run
ADPrep after Exchange 2000 has been installed without
fixing these attributes, you can end up with duplicate
schema objects with different lDAPDisplayName attributes.
To solve the problem, you must run the
inetorgpersonfix.ldf file that is located in \support\
tools\support.cab. This LDIF file fixes the
lDAPDisplayName attributes of the three attributes.
First save the inetorgpersonfix.ldf file, then import it
using the ldifde utility. Here is an example where we will
be importing into the mycorp.com forest:
ldifde.exe /i /f inetOrgPersonFix.ldf /c "DC=X"
"DC=mycorp,DC=com"
Note that inetorgpersonfix.ldf uses DC=X as the forest
path, which is why we needed to use the /c switch to
replace it with our own forest path.
Windows 2003. If we ran forest prep and domain prep
before installing exchange 2000 does this apply?
Thanks Keven
Exchange 2000
If you've installed Exchange 2000 into the forest before
running AD Prep, you have to correct some mistakes that
were made in the Exchange 2000 schema extensions.
Specifically, both ADPrep and Exchange 2000 define
labledURI, houseIdentifier and secretary attributes, but
Exchange 2000 does not use the correct LDAP display names
(lDAPDisplayName) as defined in RFC 2798. If you run
ADPrep after Exchange 2000 has been installed without
fixing these attributes, you can end up with duplicate
schema objects with different lDAPDisplayName attributes.
To solve the problem, you must run the
inetorgpersonfix.ldf file that is located in \support\
tools\support.cab. This LDIF file fixes the
lDAPDisplayName attributes of the three attributes.
First save the inetorgpersonfix.ldf file, then import it
using the ldifde utility. Here is an example where we will
be importing into the mycorp.com forest:
ldifde.exe /i /f inetOrgPersonFix.ldf /c "DC=X"
"DC=mycorp,DC=com"
Note that inetorgpersonfix.ldf uses DC=X as the forest
path, which is why we needed to use the /c switch to
replace it with our own forest path.