It sounds like you want to take the Win2K DC you created in your test lab and install it as your production DC.
Much depends on how you created you DC in the test lab?
Active Directory Rules:
1. An NT4 PDC CANNOT exist in a Win2K Active Directory (AD) domain.
2. NT4 BDCs can coexist with Win2K DCs in a Win2K AD domain.
3. To migrate an NT4 domain to a Win2K AD domain, Win2K (and AD) MUST be installed on the NT4 PDC.
The only way you could take your test lab DC and install it in your production environment is if you did the following:
1. Forced synchronization between an NT4 BDC and the PDC.
2. Removed the BDC from you productiona environment and installed in your lab environment.
3. Promoted this BDC to PDC.
4. Installed Win2K (and AD) on this lab PDC.
Only if accomplished those tasks in that order will you be able to successfully move your lab DC. Even then you will lose any changes to the domain that occured after you removed the BDC from the domain.Also, all your present BDCs may be effectively orphaned and need to be rejoined to the domain. All workstations running NT4 and higher will need to be rejoined to the domain. Your present NT4 PDC will need to be demoted to BDC (or removed from thenetwork) BEFORE you install the Win2K DC. The bottom line is you have a LOT of work ahead of you if you continue this course of action.
Do it correctly (to ensure you conduct a PROPER migration):
1. Install Win2K (and AD) on your present PDC (assuming your present PDC will meet minimum requirements). This will effectively (and correctly) migrate all settings and accounts to the new domain.
2. Demote the lab Win2K DC (run dcpromo), join it to the production Win2K domain, and repromote it if you wish another DC. You can then choose to transfer all FSMO roles to this machine if you want to retire your original PDC.
