Tweet I recently ran across an issue with an Exchange 2010 server that was configured for a hybrid Office 365 … Continue reading Exchange and the Default Domain Controllers GPO
Tweet Ok, sorry for the delay, but I want to dive right in. Let’s break down the steps from part … Continue reading Domain-wide Time Synchronization: Part 2
A customer was complaining that their “sysvol” share on their Windows Server 2003 R2 domain controllers was not replicating content (updated group policies, login scripts, etc.). Upon initial examination, I ran across this error in the event logs:
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13559
Time: 6:53:52 AM
The File Replication Service has detected that the replica root path has changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path.
This was detected for the following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Changing the replica root path is a two step process which is triggered by the creation of the NTFRS_CMD_FILE_MOVE_ROOT file.
 At the first poll which will occur in 60 minutes this computer will be deleted from the replica set.
 At the poll following the deletion this computer will be re-added to the replica set with the new root path. This re-addition will trigger a full tree sync for the replica set. At the end of the sync all the files will be at the new location. The files may or may not be deleted from the old location depending on whether they are needed or not.