i got the same event id 13566 stating that the File Replication Service is scanning the data in the system volume when i try to restore the domain controller in the virtual lab (for testing ) by using windows bare metal recovery and the sysvol share didn't
created and the domain controller didn't work his function
How to rebuild the SYSVOL tree and its content in a domain
support.microsoft.com/kb/315457
1-On the reference domain controller, build a good set of policies and scripts, and then put them in a temporary folder outside the SYSVOL replica set folders on the FRS reference domain controller
by other meaning
Move all files and folders that should reside in the SYSVOL tree to a temporary folder on the reference domain controller. The temporary folder should be located on the same partition the SYSVOL
tree is located.
2-Restart the FRS on the reference domain controller with the D4 registry entry set.
To configure the SYSVOL replica set to be authoritative, follow these steps:
- Click Start, click
Run, type regedit, and then click OK.
- Locate and then click the BurFlags entry under the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Cumulative Replica Sets\<var>GUID</var>
<var>GUID</var> is the GUID of the domain system volume replica set that is shown in the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Replica Sets\<var>GUID</var>
- Right-click BurFlags, and then click
Modify.
- Type D4 in the Value Data field (HexaDecimal), and then click
OK.
3-On the reference domain controller, move the policies and scripts folders and the folder contents from the temporary location that you used in step 1 to the FRS replica set root folder. For the SYSVOL folder, the default location for the replica set
root is the following folder:
C:\WINNT\SYSVOL\domain
-
Edited by
Minammx
Friday, December 26, 2014 9:49 PM
-
Proposed as answer by
Minammx
Friday, December 26, 2014 9:49 PM