Dear Customer,
Based on my research since receiving your post, here I provide some suggestions to resolve this issue:
1. To extend the Active Directory Schema in the existing Windows 2000 domain, by running the following commands:
a. Adprep /forestprep
b. Adprep /domainprep
2. To change the DNS info from Network adapter at new Windows Server 2003 to look up the old Windows 2000 DC.
3. To promote the 2 Windows Server 2003 to the existing Windows 2000 domain, by running “DCPROMO.EXE”
4. To install DNS Server during promotion from both DCs
5. To validate the new Windows Server 2003 DCs, by running the following
commands:
a. Net share Does NetLogon and SYSVOL exist.
b. Repadmin /syncall Make sure no error.
c. Repadmin /showrepl Make sure no error.
6. To promote 2003 DC to GC from DSSITE.MSC, then validate the DCs by running the following command:
a. Repadmin /options ß Make sure IS_GC displayed
7. To transfer the fsmo role to new 2003 DC
8. To change the DNS info from Network adapter at new Windows Server 2003 DCs to look up itself (such as 127.0.0.1)
9. To change the DNS info from Network adapter at every domain members
10. To demote gracefully the 2 existing 2000 DCs to member server
11. To uninstall DNS Server, if installed, from the old Windows 2000 DCs
12. To change the DNS info from Network adapter at old Windows 2000 to look up the new Windows Server 2003 R2 DNS Server.
Operations that are performed by the Adprep.exe utility when you add a Windows Server 2003 domain controller to a Windows 2000 domain or forest
http://support.microsoft.com/kb/309628
Enhancements to Adprep.exe in Windows Server 2003 Service Pack 1 and in hotfix 324392
http://support.microsoft.com/default.aspx?scid=kb;EN-US;324392
If there are any concerns and questions on the above, please feel free to let me know.
Sincerely
Tom Zhang
Tom Zhang – MSFT
