event ID 13568 domain controller

Note:backup of sysvol folder(Policies & Script)

troubleshoot the journal wrap, see the following article in the Microsoft Knowledge Base:

Troubleshooting Journal_Wrap Errors on Sysvol and DFS Replica Sets

http://support.microsoft.com/?id=292438

Stop FRS
Start Registry Editor (Regedt32.exe)
Locate and click the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\

NtFrs\Parameters\Backup\Restore\Process at Startup

On the Edit menu, click Add Value , and then add the following registry value:
Value name: BurFlags
Data type: REG_DWORD
Radix: Hexadecimal
Value data: D2
Quit Registry Editor
Restart FRS

Fix Journal Wrap

Click on Start, Run and type regedit

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
“System\CurrentControlSet\Services\NtFrs\Parameters”
Double click on the value name
Enable Journal Wrap Automatic Restore
and update the value

If the value name(Enable Journal Wrap Automatic Restore) is not present you may add it with the New->DWORD Value and set the value to 1 and restart FRS service
Once the recovery is completed make sure that the Enable Journal Wrap Automatic Restore is set to 0 or delete the key

Normally for an Authoritative Restore you stop at NTFRS services on all DCs
Set burflags to D4 on a known good sysvol (or at this time restore sysvol data from backup then set burflags to D4) then start NTFRS on this server You may want to rename the old folders with .old extensions prior to restoring good data
Clean up the folders on all the remaining servers (Policies Scripts etc) – renamed them with .old extensions
Set burflags to D2 on all remaining servers and start NTFRS
Wait for FRS to replicate
Clean up the old stuff if things look good

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *


CAPTCHA Image
Reload Image

This site uses Akismet to reduce spam. Learn how your comment data is processed.

WhatsApp Logo IT World