Adding 2003 Domain Controller to 2000 Domain

[jocasio]

All:

I was in the process of promoting my 2003 server to DC in my 2000 enviroment, when I got an error message stating I had to run adprep. Looking deeper into the KB articles at MS, I discovered that the 2003 schema has been modified for AD in 2003. The articles goes onto say property magling is known to occur if you are also running Exchange 2000 on the DC. Has anyone experienced this and used the resolutions to this issue?

Is there anything that can be done or any tool out there that will make this process error proof?

Please let me know if there is anything that can be done.

Thanks

jocasio

 

[markdmac]

From the schema master run ADPREP /FORESTPREP
From the domain naming master run ADPREP /DOMAINPREP

I have run this without error in a similar configuration. As always however, make a backup before you do the change and verify the backup is good.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[mlichstein]

adprep /domainprep should be run on the infrastructure master, not the domain master. If those roles are on the same machine, it doesn't matter, but if they are separated, it does.

 

[mlichstein]

Also, AD forests are NOT vulnerable to managled attributes in the following cases:

1. 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.

2. 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.

3. 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

Mangled attributes WILL occur in the following cases:

1. 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.

2. 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.

See this article for more information on how to proceed:

http://support.microsoft.com/default.aspx?kbid=325379

 

[markdmac]

My bad, thanks for pointing that out mlichstein.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[jocasio]

All:

Thanks for the help. I actually read that KB article as well as the one for Correcting the Exchange 2000 attribute mangling. I just sure if anyone has run into problems using hese recommendations. I have SBS 2000 so the infrastructure master as well as the domain master are the same box.

thanks again,

jocasio

 

[clancyfan]

I need to perform the same procedure on a network running two 2000 Servers as domain controllers and one 2000 Server as a member server running Exchange 2000.

I have a new Windows Server 2003 that is currently running as a member server that I want to promote to an additional domain controller.

My question regarding the mangled attributes re the Exchange server is:

If the Exchange server is NOT a domain controller do I need to worry about the mangled attribute issue as I will not be running adprep on the Exchange server directly?

 

[clancyfan]

Has anyone experienced the issue above? I plan to do the upgrade very soon.

 

[clancyfan]

All went well with the upgrade, following the instructions for fixing the mangled attributes.