adprep /forestprep There is a schema conflict with Exchange 2000

Hi Guys,

I'm adding a new windows 2k3 server to my 2k windows domain i want the new server to be a DC

When i ran /forestprep i got the follwing error

"Adprep was unable to extend the schema.
[Status/Consequence]
There is a schema conflict with Exchange 2000. The schema is not updated.
[User Action]
The schema conflict must be resolved before running adprep. Resolve the schema conflict, allow the change to replicate between all replication partners, and then run Adprep. For information on resolving the conflict, see Microsoft Knowledge
Base article Q325379."

I have a windows 2000 SP4 server which is the main domain controller as well as the schema master
I have a separate windows 2000 SP4 server which has exchange 2000 and is a BDC
I have another Windows 2000 SP4 server which is just a member server
There is windows 2003 server SP1 which is just a member server no AD in it.
And the new windows 2003 SP1 server which I want to make a DC

After i got the above error i did some reading and found some articles covering from InetOrgPerson to Mangled Attributes in windows 2000 forest

Here is what I have tried

Microsoft Article ID : 324392
Enhancements to Adprep.exe in Windows Server 2003 Service Pack 1 and in hotfix 324392

I'm using what i beleive is the latest adprep from the windows server 2003 SP1 Disc

adprep.exe 432KB (442,880bytes) March 25 2005 7:00:00 AM
the error message directs me to see article Q325379 which is no longer available instead shows article 324392
I read this article from beginning to end and do not see a solution other that running InetOrgPerson Fix.


Microsoft Article ID : 314649
Windows Server 2003 adprep/forestprep command causes mangled attributes in windows 2000 forest containing exchange 2000 servers
 
In this article there were three scenarios and i tried number 2 and 3 here is what microsoft said in the 2 scenarios I'm not sure if i'm doing something wrong with this procedures or if there is something wrong elsewhere but i still get the same original error.

I don't even see any records being mangled in the schema

Any help would appreciated.

Wilson J

********************************************************************************************************************************************************************************************************************
Microsoft Article ID : 314649

Scenario 2: Exchange 2000 Schema Changes Are Installed Before You Run the Windows Server 2003 adprep /forestprep Command
If Exchange 2000 schema changes have already been installed, but you have not run the adprep /forestprep command in Windows Server 2003, consider the following action plan: 1. Log on to the console of the schema operations master by using an account that is a member of the schema administrators enterprise administrators groups.  
2. Enable Schema Updates on the schema master. For additional information about how to permit updates to the Active Directory schema, click the following article number to view the article in the Microsoft Knowledge Base:
285172 (http://support.microsoft.com/kb/285172/EN-US/) Schema Updates Require Write Access to Schema in Active Directory  
3. Click Start, click Run, type notepad.exe, and then click OK.
4. Copy the following text that appears between [start copy here] and [end copy here] (including the trailing "-" characters), and then paste this text into Notepad.

[start copy here]
dn: CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,DC=X
changetype: Modify
replace: lDAPDisplayName
lDAPDisplayName: msExchAssistantName
-

dn: CN=ms-Exch-LabeledURI,CN=Schema,CN=Configuration,DC=X
changetype: Modify
replace: lDAPDisplayName
lDAPDisplayName: msExchLabeledURI
-

dn: CN=ms-Exch-House-Identifier,CN=Schema,CN=Configuration,DC=X
changetype: Modify
replace: lDAPDisplayName
lDAPDisplayName: msExchHouseIdentifier
-

dn:
changetype: Modify
add: schemaUpdateNow
schemaUpdateNow: 1
-
[end copy here]
5. Save the contents of the Notepad file as %systemdrive%\IOP\Inetorgpersonprevent.ldf (where %systemdrive% is the logical drive that is hosting the Windows 2000 operating system and \IOP is a folder that you create in the Save dialog box of Notepad. Quit Notepad.
6. Run the InetOrgPersonPrevent.ldf script: a.  Click Start, click Run, type cmd, and then click OK.
b.  At a command prompt, type :
cd %systemdrive%\iop
and then press ENTER.
c.  Type the following command:
ldifde -i -f inetorgpersonprevent.ldf -v -c DC=X "dn path for forest root domain"
where X is a case-sensitive constant and dn path for forest root domain is the domain name path for the root domain of the forest enclosed in quotation marks ("dc=corp,dc=tailspintoys,dc=com") is the domain name path for the root domain of the forest. (Include the quotation marks.) Press ENTER.
 
7. Verify that the LDAPDisplaynames for the CN=ms-Exch-Assistant-Name, the CN=ms-Exch-LabeledURI, and the CN=ms-Exch-House-Identifier attributes in the schema naming context now appear as msExchAssistantName, msExchLabeledURI, and msExchHouseIdentifier before you run the Windows Server 2003 adprep /forestprep command.
8. Run the adprep /forestprep command and the /domainprep command.

For more information, view the "Overview: Upgrading Windows 2000 Domain Controllers to Windows Server2003" section of the following Microsoft Knowledge Base article:
325379 (http://support.microsoft.com/kb/325379/) How to Upgrade Windows 2000 Domain Controllers to Windows Server 2003  


********************************************************************************************************************************************************************************************************************

Scenario 3: You Did Not Run InetOrgPersonfix Before You Ran the Windows Server 2003 adprep /forestprep Command
If you run the Windows Server 2003 adprep /forestprep command in a Windows 2000 forest that contains the Exchange 2000 schema changes, the LdapDisplayname attributes for houseIdentier, Secretary, and labeledURI become mangled. To identify mangled names, use Ldp.exe to locate the affected attributes: 1. Install Ldp.exe from the Support\Tools folder of the Windows 2000 or the Windows Server 2003 media.  
2. Start Ldp.exe from a domain controller or a member computer in the forest. a.  On the Connection menu, click Connect, leave the Server box empty, type 389 in the Port box, and then click OK.
b.  On the Connection menu, click Bind, leave all the boxes empty, and then click OK.
 
3. Record the distinguished name path for the SchemaNamingContext attribute.

For example, for a domain controller in the CORP.ADATUM.COM forest, the distinguished name path would be CN=Schema,CN=Configuration,DC=corp,DC=adatum,DC=com.
4. On the Browse menu, click Search.
5. Configure the following settings: • Base DN: Type the distinguished name path for the schema naming context that is identified in step 3.
• Filter: Type (ldapdisplayname=dup*).
• Scope: Click Subtree.
 
6. Mangled HouseIdentifier, Secretary, and LabeledURI attributes have LDAPDisplayName attributes that are similar to the following format:
lDAPDisplayName: DUP-labeledURI-9591bbd3-d2a6-4669-afda-48af7c35507d;
lDAPDisplayName: DUP-secretary-c5a1240d-70c0-455c-9906-a4070602f85f
lDAPDisplayName: DUP-houseIdentifier-354b0ca8-9b6c-4722-aae7-e66906cc9eef
If the LDAP Display names for LabeledURI, Secretary and HouseIdentifier were mangled, run the Windows Server 2003 InetOrgPersonfix.ldf script to recover:a.  Create a folder named %Systemdrive%\IOP, and then extract the InetOrgPersonfix.ldf file to this folder.  
b.  At a command prompt, type cd %systemdrive%\iop, and then press ENTER.
c.  Extract the InetOrgPersonfix.ldf file from the Support.cab file that is located in the Support\Tools folder of the Windows Server 2003 installation media.
d.  From the console of the schema operations master, load the InetOrgPersonfix.ldf file by using Ldifde.exe to correct the LdapDisplayName attribute of the houseIdentifier, the Secretary, and the labeledURI attributes. To do this, type the following command, where X is a case-sensitive constant and dn path for forest root domain is the domain name path for the root domain of the forest wrapped in quotation marks:
ldifde -i -f inetorgpersonfix.ldf -v -c DC=X "dn path for forest root domain"
 
7. Verify that the houseIdentifier, the Secretary, and the labeledURI attributes in the schema naming context are not mangled.
8. Use Winnnt32.exe to upgrade the Windows 2000 domain controllers.

For additional information about how to upgrade a Windows 2000 domain controller with Winnt32.exe, click the following article number to view the article in the Microsoft Knowledge Base:
325379 (http://support.microsoft.com/kb/325379/EN-US/) How to Upgrade Windows 2000 Domain Controllers to Windows Server 2003  

**********************************************************************************************************
**********************************************************************************************************

Start Free Trial