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

Windows Server 2012 AD-Role activation fails

Hello everybody,

we have a problem on which i got stuck for the moment.
To the history:

We took over a new customer who was the meaning, he is running 2 DCs, one Windows 2008 R2 and one Windows Server 2003. When we took over the customer we saw, that the Windows 2003 Server was already crashed and not working anymore.

Now of course we wanted to implement another DC with an actual OS Windows Server 2012.
Installation and integration to the Domain was fine, but activate the AD-Role failed.
Message: AD is running in an Windows 2000 Version!?

Trying to read out the AD Shema Version on the Windows 2008 Server responses an empty Attribut of the ObjectVersion.

Now i am a little bit stuck because recovery of the old Windows Server DC is impossible due to the fact of an missing backup of the previous service provider.

Can anybody give me a hint into the right direction what what could be the next steps?
Thanks in advance,
  • 2
1 Solution
Mike KlineCommented:
Did the box that crash hold any FSMO roles? If id did seize them to the 2008 box.

Did you cleanup that dead DC from AD  


Also check the forest, Domain functional level should be Windows 2003 and above for introducing windows 2012 server in the existing environment. If FSMO role server is server 2008 you can raise the functional level to 2008.



itechpartnerAuthor Commented:
Hey Mike, Hey Jai,

checked the various informations you sent.
Now there is some interesting outcome:

The query:
Dsquery * cn=schema,cn=configuration,dc=customerdomain,dc=local -scope base -attr objectVersion gives back a result of 47
ad version result47 = Windows Server 2008 R2
Now trying again to upgrade the new installed Windows Server 2012 to an DC and bind it to an existing domain fails with the already known results:
failure message...."Failure by check of the replicate. The Structure is Windows 2000. If you want to install a Windows Server 2012 as an Domain-Controller the structure should be higher than 2000."...
How can that be?"
Check the forest and domain functional level. If any of the level is still in windows 2000 you cannot introduce the 2012 as DC. you need to raise it to 2003.



Make sure you don't have 2000 systems in your environment before proceeding further.
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

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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