Using 2nd dom contrlr for transition

well, this is a really great opportunity for you. lucky dog.
you really need to study the network to see what you have. perhaps you have nt security structure, perhaps you have new active directory (which will probably make this cake).
check out http:www.microsoft.com/technet
pick How To Resources (left)
then Windows 2000 Server How To
for articles such as:
Deploy
Migrate Users from NetWare to Windows 2000 with the MSDSS Tool and One-Time Migration
Integrate Windows 2000 DNS with an Existing DNS Infrastructure in Windows 2000
Integrate Windows 2000 DNS with Existing DNS Infrastructure If Active Directory Is Enabled
Upgrade Your Windows NT Server Version 4.0 to Windows 2000 Server
Establish Trusts with a Windows NT-Based Domain
Migrate an Existing Domain Name System Infrastructure from a BIND-Based Server to a Windows 2000-Based Domain Name System Server
Replace the Current Primary DNS Server with a New Primary Windows 2000 DNS Server
Set Permissions for Pre-Staged Computers By Using Remote Installation Services

Operate/Administer
Mirror the System and Boot Partition (RAID1)
Establish a Striped Volume (RAID 0)
Establish a Striped Volume with Parity (RAID-5)
Prevent Users from Scheduling Tasks
Use the Backup Wizard for Backup Jobs
Install the Active Directory Administrative Tools to Windows 2000 Professional
Configure Windows 2000 Server to Inform You When Your Computer Resources Are Running Low
Enable and Apply Windows Security Auditing
Create a New Zone on a DNS Server
Configure Network Load Balancing Parameters
Support/Troubleshoot
Back Up and Restore the System State Using the Windows 2000 Backup Program
Diagnose System Problems with Event Viewer in Microsoft Windows 2000
Install the Windows 2000 Support Tools to a Windows 2000 Server-Based Computer
Recover a Windows 2000 Server that Does Not Start

This is easy.
1.Install Windows 2000 server SP4 on a second box (different machine name from the main DC)
1a. configure the IP address to be on the same subnet as the main DC
2.point its primary DNS configuration to the main DC.
3.join this server to your production domain.
4.run DCpromo and make it a replica DC in your domain.
5.Your main DC should have the DNS zone as an active directrory integrated zone to minimize the steps required.
6.Once the second DC is up and functioning, then you can migrate services to the new DC. file, print, email, DHCP etc. (do this during non business hours)
7.reconfigure the primary DNS pointer on the new server to point to itself for name resolution.
8.reconfigure clients to point to the IP address of the new DC for name resolution. through DHCP or manually if the clients are statically configured.
8a. any mapped drives which reference the old server will need to be updated to the new server
9.run dcpromo on the old DC to demote it to a member server. This will remove AD and transfer all the FSMO roles to the new DC.
10. Turn the old box off, delete the machine account in AD and you are done. :-)

Glenn

This question was closed by the author