<div>
Could you post results from DCDIAG from DC1 &amp;&nbsp;DC2
</div>


<div>
both servers report no errors from their dcdiag.
</div>


<div>
Follow this link:<br />
<br />
<a href="https://social.technet.microsoft.com/Forums/windowsserver/en-US/b8551825-67e1-4da7-8cbb-563246c1b603/solved-sysvol-does-not-replicate-between-dcs?forum=winserverGP" rel="ugc nofollow">https://social.technet.microsoft.com/Forums/windowsserver/en-US/b8551825-67e1-4da7-8cbb-563246c1b603/solved-sysvol-does-not-replicate-between-dcs?forum=winserverGP</a>
</div>


<div>
yup i have that object in adsi edit.
</div>


<div>
never used that let me go see how it works. thanks.,
</div>


<div>
so without the even viewer being coutned it passed the tests.<br />
It fails when i include the event viewer because of <br />
<br />
The File Replication Service has detected that the replica set &quot;DOMAIN SYSTEM VOLUME (SYSVOL SHARE)&quot; is in JRNL_WRAP_ERROR.
</div>


<div>
Greg once i run all this it seems my times dont match on the folders in the sysvol shares should it be exactly the same?
</div>


<div>
Not necessarily.<br />
<br />
What is event viewer telling you? &nbsp;you should see events related to FRS replication status
</div>


<div>
it acts like its all fine and dandy but none of my changes ever appear on the other DC. Also a policy i made last week does not work now, oh boy!
</div>


<div>
good thing i backed it up right greg haha.<br />
So i just deleted everything from the polic folder on the live sysvol share and i saw it remove it from the other DC. Ok... then i moved all of my policies from my backup back into the sysvol share on the main dc and they went right over to the backup. Guess i will keep messing around with editing the actual gp and seeing if they change on the other server. thanks greg.
</div>


<div>
<div class="content wysiwyg-content">
Hi<br />
I have noticed my sysvol is not going from my main DC to my secondar DC. <br />
I got error 13568 the good ol wrap message a lot of people seem to get.<br />
However i have a question<br />
I see many articles about changing the reg key to either d2/d4 to do a restore.<br />
What one do i use... here is my topology.<br />
DC1 is the main and i make all my GP changes here. It is not replicating sysvol to DC2.<br />
DC2 is my backup server per say. Its sysvol is old.<br />
However i ran many replication/dns tests and everything is fine, just seemed like this sysvol is my prob and not something else in AD that i can see.
</div>
</div>


Hi
I have noticed my sysvol is not going from my main DC to my secondar DC. 
I got error 13568 the good ol wrap message a lot of people seem to get.
However i have a question
I see many articles about changing the reg key to either d2/d4 to do a restore.
What one do i use... here is my topology.
DC1 is the main and i make all my GP changes here. It is not replicating sysvol to DC2.
DC2 is my backup server per say. Its sysvol is old.
However i ran many replication/dns tests and everything is fine, just seemed like this sysvol is my prob and not something else in AD that i can see.

Sysvol Not Replicating

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.