New DC 2003

Currently we are running 2 windows 2000 DC's. One is our DHCP, DNS, WINS and
File Server. The other is our Mail server. We are getting a new Windows
2003 server that I would like to take over for the current server running
DHCP, DNS, WINS and file server. I know I have to bring up the server and do
a DCPromo. Whatelse would I need to do to get this new server into the
domain as a DC and move all information over (ie., DHCP, DNS & WINS) from the
old 2000 server. We just got done with a re IP of the whole network and the
last thing I want to do is reboot all PC's again, so there must be a painless
way of doing this.

The process is basically:

1. If Exchange 2000 is installed in the forest run the InetOrgPerson fix
prior to the schema update (see below), or upgrade it to Exchange 2003.
2. Run adprep /forestprep (must be able to connect to Schema Master to do
this)
3. Run adprep /domainprep
4. Run DCPROMO on any 2000 DC
5. Verify functionality of the domain, then promote the other two 2000 DCs.

Upgrading Windows 2000 Domains to Windows Server 2003 Domains:
http://www.microsoft.com/resources/d...n_overview.asp

Regarding the mangled attribute problem:
If you have already upgraded to Exchange 2003 than you don't need to run the
InetOrgPerson fix. See:
http://support.microsoft.com/default.aspx?kbid=314649

Export (Backup) Tools DHCP, DNS, WINS:

Use DHCPExim.exe from:
http://www.microsoft.com/windows2000...dhcpexim-o.asp

For a Windows Server 2003 DHCP Server-
How to move a DHCP database to a computer that is running Windows Server
2003:
http://support.microsoft.com/default...uct=winsvr2003

-----------------------------------------------------------------------------------------

Dnscmd.exe from the Win2000 Support Tools on the Windows 2000 Server CD-ROM
(Support\Tools folder). DNSdump at www.reskit.net/scripts will export
and/or import the zone data and registry entries. It will move/copy zones
and registry entries. Even supports a migration from Windows NT4.0 to
Windows Server 2003.

How to move Windows 2000 DNS zones to another Windows 2000-based server:
http://support.microsoft.com/Default.aspx?kbid=280061

Alternatively, if the existing DNS zones are of the standard primary type
and exist on Microsoft DNS servers, then they are stored in text files
located under \%Systemroot%\System32\DNS. Simply copy these files in
\%Systemroot%\System32\DNS to your new DNS server. Create the new zones
choosing import from file as the source during the zone creation wizard. If
you would prefer that these zone be ADI, then you can change the type to
AD-integrated after the wizard completes. If the existing zone type is
Active Directory-integarted (ADI), then prior to the export, simply convert
the zone from ADI to standard primary type, then convert the zone back to
ADI after the wizard completes.

-----------------------------------------------------------------------------------------

Use Resource kit utility WINSDMP to export the WINS database.

Finally, regarding transferring roles:

FSMO movement:
http://support.microsoft.com/default...roduct=win2000

FSMO placement:
http://support.microsoft.com/default...b;en-us;223346

Using Ntdsutil.exe to seize or transfer FSMO roles to a domain controller
http://support.microsoft.com/default...uct=winsvr2003

Don't forget you still need at least one global catalog server when
migration is completed.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT