Join Server 2008 DC to 2000 Domain

You need to remove this domain controller (2000) from the domain and then make sure that you are running a 2003 Forest and domain functional level. After that you can prep the 2003 forest/domain and then you can introduce your first 2008 DC.

Will.

I can't do an AD prep and join it?

This is 64 bit.

You will have to run ADPREP32.exe from the installation CD\DVD on the Windows 2000 DC.

To prepare the domain, run Adprep.exe from the installation DVD on your existing domain controller that hosts the infrastructure master role. In Windows Server 2008, Adprep.exe is located in the /Sources/adprep folder of the operating system installation DVD. In Windows Server 2008 R2, Adprep.exe is located in the /Support/adprep folder.

Source

-saige-

Okay, please check my steps below:

-So take a system state backup of the 2000 DC.
-raise DFL and FFL to 2000 native/Windows 2000
-Run Adprep32 from sources/adprep on the 2000 DC.
-Promote 2008 DC to environment.

Is that correct?

Windows Server 2008  includes a 32-bit and 64-bit version of Adprep.exe. The 64-bit version runs by default. If you want to run one of the Adprep.exe commands on a 32-bit computer, use the 32-bit version of Adprep.exe (Adprep32.exe).

Thanks, what should do i do to my sole 2000 DC in case something doesnt go right and need to roll back?

That is about the size of it.  Only thing I might add is a check of the current health of the domain.

http://blogs.technet.com/b/ptsblog/archive/2011/11/14/performing-an-active-directory-health-check-before-upgrading.aspx

Be warned, not all of the tools listed are available for Windows 2000, and most (for example, dcdiag require Service Pack 3 or higher).

-saige-

Is a system state a good backup?

There are no file or other shares on the DC.

For Active-Directory, yes:

Active Directory is backed up as part of system state, a collection of system components that depend on each other. You must back up and restore system state components together.

Components that comprise the system state on a domain controller include:
• System Start-up Files (boot files). These are the files required for Windows 2000 Server to start.
• System registry.
• Class registration database of Component Services. The Component Object Model (COM) is a binary standard for writing component software in a distributed systems environment.
• SYSVOL. The system volume provides a default Active Directory location for files that must be shared for common access throughout a domain. The SYSVOL folder on a domain controller contains:
◦NETLOGON shared folders. These usually host user logon scripts and Group Policy objects (GPOs) for non-Windows 2000based network clients.
◦User logon scripts for Windows 2000 Professionalbased clients and clients that are running Windows 95, Windows 98, or Windows NT 4.0.
◦Windows 2000 GPOs.
◦File system junctions.
◦File Replication service (FRS) staging directories and files that are required to be available and synchronized between domain controllers.
• Active Directory. Active Directory includes:
◦Ntds.dit: The Active Directory database.
◦Edb.chk: The checkpoint file.
◦Edb*.log: The transaction logs, each 10 megabytes (MB) in size.
◦Res1.log and Res2.log: Reserved transaction logs.

Note: If you use Active Directory-integrated DNS, then the zone data is backed up as part of the Active Directory database. If you do not use Active Directory-integrated DNS, you must explicitly back up the zone files. However, if you back up the system disk along with the system state, zone data is backed up as part of the system disk.If you installed Windows Clustering or Certificate Services on your domain controller, they are also backed up as part of system state. Details of these components are not discussed in this guide.

Source

-saige-

After the journal wrap fix, everything is now healthy.