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

New Domain Controller FRS error

Three days ago, I promoted a new 2012 R2 server to a domain controller.  I keep checking to see if the sysvol is shared and it is not, so I looked at the event logs.  (FYI: Currently, our domain is still transitioning from FRS to DFS replication of the sysvol.  The global state is "Redirected".  Not sure if that has any bearing on the situation.)  We are getting the event 13508 twice every day since the promotion, but we never got the 13509 event.  It is trying to replicate from a server in the same site (Windows Server 2008).  I have verified that the File Replication Service is running on both machines and that the new server can ping by name the server it is replicating from.  Active directory is replicating just fine.  What should I be looking at to resolve this issue?

Thanks in advance for your help.
0
ejscn
Asked:
ejscn
  • 3
  • 2
2 Solutions
 
Adam BrownSr Solutions ArchitectCommented:
What functional level are you at? Server 2012 will not receive FRS replicated SYSVOL unless the functional level is 2000 or 2003. Basically, if you're at 2008+ functional level, you will not be able to properly use a server 2012 DC until you finish migrating to DFS replication for SYSVOL.
0
 
MaheshArchitectCommented:
Run dfsrmig /getmigrationstate command on PDC master server to confirm DFSR migration reached to Redirected state

Once that confirmed, run Net Share command on affected 2012 r2 ADC and check if sysvol is replicated through DFSR

The command output should look like below
NETLOGON     C:\Windows\SYSVOL_DFSR\sysvol\corp.contoso.com\SCRIPTS
                                             Logon server share
SYSVOL       C:\Windows\SYSVOL_DFSR\sysvol   Logon server share

If you won't be able to find sysvol shared as shown above, demotion and repromotion of 2012 R2 ADC is one good option.

Install DFS management tools on domain controller and from there run DFSR propogation test for all domain controllers for verification

Check below article for more info
http://blogs.technet.com/b/askds/archive/2008/05/22/verifying-file-replication-during-the-windows-server-2008-dfsr-sysvol-migration-down-and-dirty-style.aspx

Your FRS service will also remain running and now all GPO changes, creation will be happening in DFSR Sysvol only and not with FRS sysvol.DFSR syvol is now active Sysvol Share for any operations.
FRS Sysvol is now just a folder

Also check Ad replication within Ad sites and services and check if its working correctly
Use repadmin /showrepl and repadmin /syncall commands
Also trigger replication between sites manually in AD sites and services console for confirmation

If every thing is fine, just proceed with Eliminated state

Mahesh.
0
 
ejscnAuthor Commented:
Thank you both for your answers.  I'm following your instructions, Mahesh.  I'm going through all the verification steps listed here: http://technet.microsoft.com/en-us/library/dd641340(v=ws.10).aspx before moving to the eliminated state in the DFSR transition.  About a year ago, one of our DCs failed and we reformatted it with Server 2012.  I am looking in the DFS Management console, and the failed (now non-existent) DC is showing up in the replication group as disabled.  Should I just remove it from the replication group?
0
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.

 
MaheshArchitectCommented:
You will find that DC under File replication service container and DFS container under domain.com\system container in active directory
Also you will find it within Metadata also if its not cleared properly when you demoted earlier

Just remove every possible trace of failed DC in active directory

This includes:
Domain Controllers OU (I guess its not there and already removed)
AD sites and services
domain.com\system\File replication servioces\domain system volume (Sysvol)
NS records in DNS
SRV records in DNS
Host(A) records in DNS

Check below article for metadata cleanup
http://support.microsoft.com/kb/216498
http://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx

After cleaning up traces from all above places, make sure that your DFSR sysvol is healthy with redirected state prior to moving Eliminated State
http://technet.microsoft.com/en-us/library/dd640019(v=ws.10).aspx

Mahesh.
0
 
ejscnAuthor Commented:
Mahesh,

Thank you SO MUCH for all of your great help.  The new server is up and running and the old one is gone.

Adam
0
 
ejscnAuthor Commented:
Mahesh went above and beyond with the level of detail in his responses and pointing me in the right direction for help with my problem.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

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