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

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...
0
admineo
Asked:
admineo
1 Solution
 
SandeshdubeyCommented:
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.
0
 
Mike KlineCommented:
What is the new server pointing to for its DNS settings?

Can you check your schema version   http://adisfun.blogspot.com/2013/06/windows-server-2012-r2-preview-schema.html   

I want to see if that completed?

Thanks

Mike
0
 
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.
dcdiag.txt
ipconfig.txt
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
SandeshdubeyCommented:
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.http://support.microsoft.com/kb/290762

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.
0
 
ZenVenkyArchitectCommented:
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
0
 
JaihuntCommented:
The target name used was LDAP/DE13EFCA-8F92-4C97-8E31-9CDED5EE1D
52._msdcs.xxxxDOM.local

Have you tried reset the computer account password through netdom?

http://sumoomicrosoft.blogspot.com/2012/07/reset-domain-controller-computer-account.html
0
 
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.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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