SYSVOL are not synchronized across the domain even though there are no errors in Even Logs or Diagnostic Tools...

Sorry for my english,

I have Windows Server 2003 R2 SP2 (2003 level)  domain with two domain controllers.

Even though everything seems to be working fine - DCDIAG, NTFRSUTL and other diagnostic tools do not return any errors, there's no any errors in DC's logs either, the SYSVOL shares doesn't seems to be in sync. Logon scripts modyfied on one of them are never saved to another, and  vice versa. The same situation with Group Policies.

The FRS services are running.  I was thinking that maybe they do synchronize with SYSVOL in different location on the hardrive somehow, but there doesn't seem to be any other folder identical to the sysvol on another server :/

Please advice.

dannydudekAsked:
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.

Brian PiercePhotographerCommented:
There is no SYSVOL folder on one DC or there is but its not the same?
If the former see See http://www.jsifaq.com/SF/Tips/Tip.aspx?id=7394
0
dannydudekAuthor Commented:
There are SYSVOLs but they're not the same...
0
Brian PiercePhotographerCommented:
0
dannydudekAuthor Commented:
Diagnostic showed:

      ERROR: Junction Point missing on "\\dc1\c$\windows\sysvol\sysvol"
      ERROR: Junction Point missing on "\\dc1\c$\windows\sysvol\staging areas"

However, LINKD C:\WINDOWS\SYSVOL\STAGING AREA C:\WINDOWS\SYSVOL\STAGING  doesn't seems to be solving them.

Where and what junction points should I create?
0
ocon827679Commented:
Restart the FRS service on each domain controller.  Take a look at the FRS Event log.  If everything is OK with the server then you will receive an event 13516.  This event states that sysvol is shared.  This is the last process to make the server a domain controller.  If you see an event (I forget the number) that states that the server is having problems communicating and wil try again later or that you are in a journal wrap, then sysvol is not shared and you have the problems that you describe.

On the problem DC run the procedure in http://support.microsoft.com/kb/290762/en-us  This will reinitialize FRS and bring the Sysvol's between the systems up to date.  Note that there are 2 entries for Burflags, D2 and D4.  D2 is a non-authoitative restore.  If one of your DC's is correct, then use the D2 on the problem.  If all the dc's are hosed an one is OK, then from the good one run the D4.  I prefer the D2 - its safer in my mind.
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
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 Server 2003

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.