Solved

Help for setting up replicating Sysvol between to domain controllers

Posted on 2008-11-01
5
582 Views
Last Modified: 2012-05-05
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?
0
Comment
Question by:Danny_nilsson
5 Comments
 
LVL 63

Expert Comment

by:SysExpert
ID: 22859617
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 !
0
 
LVL 6

Expert Comment

by:CorpComp
ID: 22860646
Have you checked the event log on the first server?
0
 
LVL 18

Expert Comment

by:Andrej Pirman
ID: 22860750
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.
0
 
LVL 1

Author Comment

by:Danny_nilsson
ID: 22860767
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
Server1.txt
Server2.txt
0
 
LVL 1

Accepted Solution

by:
Danny_nilsson earned 0 total points
ID: 23024672
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
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Join & Write a Comment

Have you considered what group policies are backwards and forwards compatible? Windows Active Directory servers and clients use group policy templates to deploy sets of policies within your domain. But, there is a catch to deploying policies. The…
This is a little timesaver I have been using for setting up Microsoft Small Business Server (SBS) in the simplest possible way. It may not be appropriate for every customer. However, when you get a situation where the person who owns the server is i…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now