Hi Brian,
The easiest way to fix this is the recommended way - setting the Burflags to
2 and letting FRS copy the SYSVOL from another DC. FSMO roles don't come
into this. If you've other DCs in the same site, modify the registry late
one afternoon and you'll be up and running once you've finished your coffee.
If the DCs are in another site across a WAN, make the changes to the
registry and call it a day -everything'll be fine in the morning.
As for changes, what kind of changes? As far as I'm aware a Journal Wrap
will only affect SYSVOL and DFS replicas. If you've made any changes to the
Directory this shouldn't matter. Obviously GPO modifications made on this
server since it wrapped will be lost.
Whenever I've done this I've never had problems.
However, it is a must to try and discern what caused this. As you don't
want to be doing this every couple of days. It's usually old/ bad AV or
network/ WAN problems that cause this. If the FRS log has very few warnings
it could be a one off; if there's loads of warnings in there, start looking
for the root cause of this problem, not just the solution.
Hope this helps,
Paul.
____________________________
Brian Dishong said:
I'm getting a JRNL_WRAP_ERROR on a Windows 2003 DC. It sounds to me as if
this is causing the version mismatch errors I am seeing in my GPOTOOL
report. Would the Burflags fix be appropriate for this server? Are FSMO
roles assigned to this DC going to cause any issues? I'm going to assume
that any changes made directly to this server will be lost when the restore
is completed.
