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

Posted on 2007-10-04
Last Modified: 2008-05-31
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.

Question by:dannydudek
    LVL 70

    Expert Comment

    There is no SYSVOL folder on one DC or there is but its not the same?
    If the former see See

    Author Comment

    There are SYSVOLs but they're not the same...
    LVL 70

    Expert Comment


    Author Comment

    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?
    LVL 13

    Accepted Solution

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

    Featured Post

    What Security Threats Are You Missing?

    Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

    Join & Write a Comment

    Scenerio: You have a server running Server 2003 and have applied a retail pack of Terminal Server Licenses.  You want to change servers or your server has crashed and you need to reapply the Terminal Server Licenses. When you enter the 16-digit lic…
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

    729 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

    22 Experts available now in Live!

    Get 1:1 Help Now