Server 2012 Domain Controllers not Appearing

Have a strange issue I am hoping someone can give me a hand with.

Have a 2012 domain with a single Server 2012 as PDC. Trying to add a second DC and then turn second DC into PDC. Have successfully add AD DS and new server appears in AD as a domain controller. However new DC does not have SYSVOL nor NETLOGON shares. Also when I try to change PDC in Operations Manager the new DC is not appearing.  

The original PDC does have a Post-Deployment Configuration alert to promote the new second DC to a domain controller, however their is a lengthy Windows PowerShell error shown in Attachment.  I have removed AD DS from multiple servers, all showing the same results. Have tried both GUI and PS installations with same results.

Appreciate any pointers or thoughts.

PS error when trying to promote new server to DC from PDC.
LSoltAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Lee W, MVPTechnology and Business Process AdvisorCommented:
Before attempting to add DCs you should be running DCDIAG /C /E /V on all existing DCs to ensure the health of AD.  Resolve any unexpected errors.  Once you can tell us that DCDIAG is clean, see what happens when you attempt to promote that serer as a DC.
arnoldCommented:
When you setup the first DC, was it migrated from a prior D. Setup.  My suspension is that your sysvol/netlogon shares are
1) have issues on the existing DC journal error which will prevent replication to the new DC
2) uses ntfrs for replication which you have not added under the fileserver feature/service. DO NOT add until you make sure there are no journal issues on the prior DC.
Will SzymkowskiSenior Solution ArchitectCommented:
If you have just promoted this DC and the sysvol shares were not replicated then there was some sort of communication issue during the promotion. First check your directory service logs in the event viewer. If there are errors specific to the sysvol shares not replicating what I would do is demote the DC and re-promote.

This will be the quickest and painless way to try and resolve this issue.

Make sure that there are no firewall rules blocking communication between the DC's.

Will.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

SandeshdubeySenior Server EngineerCommented:
As suggested already you need to ensure that the health of exiting DC is good before you proceed with AD promotion of new server. Run dcdiag /q and repadmin /replsum and post the log.

Ensure correct dns setting as below

Best practices for DNS client settings on DC and domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/

Also, disable local windows firewall service, by default it is enabled in vista/windows 2008 and above. Check the network connectivity and latency.
Disable Windows Firewall: http://technet.microsoft.com/en-us/library/cc766337(WS.10).aspx

Active Directory and Active Directory Domain Services Port Requirements
http://technet.microsoft.com/en-us/library/dd772723%28WS.10%29.aspx

As the new DC sysvol and netlogon share is missing you may have to perform authorative and non authorative restore of sysvol: https://social.technet.microsoft.com/Forums/windowsserver/en-US/7652f4ac-6974-4bdc-9b31-7632c85b0811/new-2008-dc-not-replicating-with-existing-2003-dcs
LSoltAuthor Commented:
Thanks all!! Starting diagnosing issues. Will update shortly.
LSoltAuthor Commented:
Completed cleaning DCDiag but still was unable to successfully repair. Threw the towel in and called Microsoft in. It appears that the issue was related to corrupt files on the PDC. They were able to repair and we successfully transferred FMSO roles to new DC. Appreciate the advise as DCDiag cleanup was something that needed to be accomplished anyway.

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
LSoltAuthor Commented:
This was something that only experienced MS engineers could have accurately identified and solved. Short of rebuilding the domain we would not have been able to repair.
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
Active Directory

From novice to tech pro — start learning today.