AD - First Server 2012 AD DS / DNS member hosed

Hello.  I have 4 existing DC's in the forest, at server 2003 functional level.  All other DC's are either Server 2003 or Server 2008.  I am wanting to decommission the 2003's and move them to 2012's so that we can work towards a higher functional level.  First things first, I build a server 2012 instance, disable firewall, run updates, and add the role.

First attempt: It fails.  Turns out joining the domain did not create itself a computer account in AD like normal.  No problem.  Remove/re-add from domain and make sure computer account is present and in the 'Domain Controllers' group.

Second attempt: It seemingly succeeds and reboots.  I have confirmed that the forest & domain were prepped and at the proper level.  However, It is not showing up as an available controller in ADUC and has all sorts of errors.  It says I need to promote, but there is an error:

DC Error 1
I cannot continue.  The DNS portion comes up with access denied.  If I open up ADUC and manually point it at the server, it does show data.  So I know the initial replication succeeded.    The Best Practices Analyzer has 68 errors:

DC Error 2
My install seems completely hosed... where should I turn next?  I could just re-format... but then i'm guessing this partially completed AD server is "stuck" somewhere in AD.  I have attempted a demotion, which fails with access denied.  I have not tried the 'Force' option yet.

Good times with Microsoft...
Who is Participating?
JaihuntConnect With a Mentor Commented:
The target name used was LDAP/DE13EFCA-8F92-4C97-8E31-9CDED5EE1D

Have you tried reset the computer account password through netdom?
SandeshdubeySenior Server EngineerCommented:
If the server wa promoted as DC open the command prompt and run dcdiag /q and post the log with ipconfig /all details of DC.
Mike KlineCommented:
What is the new server pointing to for its DNS settings?

Can you check your schema version   

I want to see if that completed?


Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

admineoAuthor Commented:
@Sandeshdubey:  See Attached.  Thanks

@mkline71:  Schema is at 56.  DNS is pointed to another DC and then itself.  You can see in the ipconfig attached.
SandeshdubeySenior Server EngineerCommented:
From the log it is clear that netlogon share is missing.Check the sysvol and netlogon share are available or not.Ran net share command to check the same.If the sysvol and netlogon share is missing that server will not act as DC.

Check the sysvol folder are the policies and script folder replicated or not.If it is not replicated you need to perform authorative and non authorative of sysvol folder to fix the same.

Kindly take the backup of the sysvol folder of DCs that is copy paste the content of the sysvol to temp location and perform the authorative and non authorative restore of sysvol as mentioned before.
Before you proceed with Sandesh's comments, I would suggest you to fix Time Synchronisation. I'm sure it is a Time Sync issue.  PDCe role holder shall point to external Time server for time sync and rest all machines in the domain shall point to PDC for time sync. Check these links for better understanding.

Authoritative Time Server

DNS Best Practices
admineoAuthor Commented:
This was absolutely the issue.  Thanks Jaihunt!

I tried the 'Repadmin /syncall' and got some crazy errors.  I followed the rest of the steps and it worked itself out.  Both AD & DNS seem to be happy.
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.

All Courses

From novice to tech pro — start learning today.