Join Server 2008 DC to 2000 Domain

Hey guys,

We have an old Server 2000 Domain Controller, and i would like to add a Server 2008 DC (non-r2) to the domain. What steps do i need to do?
LVL 4
Cobra25Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
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.
0
Cobra25Author Commented:
I can't do an AD prep and join it?
0
it_saigeDeveloperCommented:
According to: Understanding Active Directory Domain Services (AD DS) Functional Levels

Windows 2008 can be joined to a domain running in Windows 2000 native mode with a Forest level of Windows 2000.

You said this is non-R2 but which bit level (32 or 64)?

-saige-
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Cobra25Author Commented:
This is 64 bit.
0
it_saigeDeveloperCommented:
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-
0
Cobra25Author Commented:
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?
0
joenswCommented:
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).
0
Cobra25Author Commented:
Thanks, what should do i do to my sole 2000 DC in case something doesnt go right and need to roll back?
0
it_saigeDeveloperCommented:
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-
0
Cobra25Author Commented:
Is a system state a good backup?

There are no file or other shares on the DC.
0
it_saigeDeveloperCommented:
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-
0
Cobra25Author Commented:
After the journal wrap fix, everything is now healthy.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.