• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 206
  • Last Modified:

Domain controller fails to be added to domain.


I'm in the process of trying to add a domain controller to one of my domains over a VPN connection. To ensure that i have no DNS issues i have copied all the .dns files and created secondary zones on the local machine, (and confirmed that it is all populated correctly)

My forest and my existing domain controllers are raised to 2003 top level functionality.

I'm attempting to add a Windows 2003 Std R2 server as another domain controller but receive this error:

Active Directory Installation Wizard
The operation failed because:

The Active Directory Installation Wizard cannot continue because the forest is not prepared for installing Windows Server 2003. Use the Adprep command-line tool to prepare both the forest and the domain. For more information about using the Adprep, see Active Directory Help.

"The version of the Active Directory schema of the source forest is not compatible with the version of Active Directory on this computer."

I've run the command suggested on all domains in question but i still gives this error.

From what i can tell this error is to do with adding servers into a mixed 2000 and 2003 environment, but this isn't the case here.

Any ideas?

Thanks for your help

1 Solution
Your new machine is probably running W2k3 R2; you need to run an additional adprep /forestprep from \cmpnents\R2\adprep folder on the second R2 CD:
Extending Your Active Directory Schema for New Features in Windows Server 2003 R2
oBdA has probably hit the nail on the head as regards your problem.Hoerver, I an a bit concerned that you say you have 'copied all the .dns files'. Why?

You either need to make sure that the new domain controller uses active directory integrated DNS or you need to delegate and/or set up a traditional DNS secondary zone. Whatever the option you do not need to manaully copy the .dns files.

One other point, while you are in the process of promoting the new domain controller, make sure it has the existing machine set as its Preferred DNS server.
kadadi_vIT AdminCommented:
u should have global catalog server connectivity and domain naming rules accessible by the new server .
kiwiplanAuthor Commented:
Thanks for your help guys your were right onto it there.

As the for DNS I was having problems getting it to replicate so i attempted to get around it using the .dns files copied manually.
This turned out as you'd probably expect to be a bad idea and when i added the domain controller it only updated its local dns info rendering the whole thing a mess.

So i reinstalled, Restarted, fixed DNS replication, added domain and now all is well!

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.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now