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

Help for setting up replicating Sysvol between to domain controllers

I have spend about 20 hours on troubleshooting problems with FRS and inconsistency of topology. but after demoting and following many guides i have acomplished to get logs clean and ntfrsutl.exe with passed on all tests. sonars also got passed on sysvol. but on my DC1 i godt datacollectionstate failed, out of what i can read this doent have to be a problem. i also tried repadmin  also with out errors. so my question is im kind of new i setting up SYSVOL and thought W2K3 automatic created and configured those folders when join as a domain controller. also my eventlog dont have any errors.

what i have tried was moving the files from DC1 to another folder and setting the burflag to D2 and restarting FRS and copy the files back and try from sites and services and press replicate now. from site and services i also a littlebit unsure how to excly set it up. i have activated global catalog on the DC2 after joining

but maybe i need a little bit extra before they sync?
1 Solution
It is supposed to be automatic.

I would run DCDIAG and netdag in verbose mode to a log file and see what they show.

I hope this helps !
Have you checked the event log on the first server?
Andrej PirmanCommented:
Run "GPOTOOL" command on any DC and it will show group policy consistency on all DC's. If they are fine, then you may try manually creating some file on one DC in \SYSVOL folder, and wait at least 15 minutes to see if file replicated to other DC.

If you get error with GPOTOOL, see, which group policy is failed and do some insignificant change within this policy on any DC. Doing so, the whole group policy will rewrite itself, and correct possible error.

Maybe this would help.
Danny_nilssonAuthor Commented:
Yes the event logs show up fine after running meta clean up and rejoining the server. but after the server was rejoined the sysvol didnt work automatic

all the problem has starting because im a new it guy in this company where the old guy never used a event log so i have tried getting all these errors away. the server 2 has just been running as logon server and file/print server so its possible that this one can have some other problems thats not related to this problem. server 1 is running sbs and all the services like exchange & sharepoint.

Server 2 has exchange installed but not used anymore so that will be another project to uninstall and clean the event on this server
Danny_nilssonAuthor Commented:
I found the solution by myself. it appeard to be some corrupt reg enteries. i could see it was not the same when compared the Nfr reg. with the server that seemed to work. and after i copied the hold nfr branch and created the site connection again. it begin to replicate and my Sonar for diagnose didnt fail anymore

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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