Windows 2008 R2 Domain Controller Sysvol Replication Broken

We currently have 2 domain controllers both running 2008 R2.  We only have 1 forest with 1 domain.  DC1 is the PDC, and DC2 the other domain controller.  I am trying to troubleshoot why sysvol is not replicating and found the following information.  We are using DFSR for replication.

When I view the "Domain System Volume" using the DFS Management snap-in, I see the membership status enabled for both domain controllers.  However the "local path" is not defined.  When I open ADSIEDIT, and go to DC=Domain, OU=Domain Controllers, CN=DC1, CN=DFSR-LocalSettings, CN=Domain System Volume, I see nothing else.  There is nothing inside of Domain System Volume.  Same goes for DC2.  However for the DFSR-GlobalSettings I do see data in there.  Seems like its the Localsettings that have been wiped out.

Our "Windows admin" recently left, and I am stuck with this heap of a mess.

The actual location of the sysvol share on DC1 for example is fully populated with the policies.  It just seems the replication is not working, and after he took a look at it before he left, now some of the settings are missing.

Please HELP!
spadmin1Asked:
Who is Participating?
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.

MaheshArchitectCommented:
If you have valid system state backup, you need to restore it authoritatively
OR
you need to manually create directory structure in active directory

DFSR-Subscription component is missing under Domain System volumemain system volume and create new objetc through adsiedit.msc

U might check those entries with some healthy ad infra at lab etc
0

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
SteveCommented:
check eventvwr (system, application, directory service & frs) to see whats there relating to DC, netlogon,AD etc on both DCs.
run 'DCdiag' on both servers and post results (after amending the server names for privacy if necessary)
0
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
Windows Networking

From novice to tech pro — start learning today.

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.