In my situation I created a text file with that name in the C:\WINDOWS\SYSVOL\domain directory on the domain controller.Ģ. Create a file named NTFRS_CMD_FILE_MOVE_ROOT in the directory listed in the event description where the replica root path has been moved to. To fix the problem here's what you should do, assuming you have another domain controller that you can pull a new set of SYSVOL data fromġ. There's also KB 819268, but I didn't really find it useful. I did a little research and found that all I needed to do was listen to the event description and create the file requested. I didn't change the location of sysvol, and according to the event the sysvol location was changed to the same location.
If this is an intentional move then file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path.' 'The File Replication Service has detected that the replica root path has changed from 'c:\windows\sysvol\domain' to 'c:\windows\sysvol\domain'. After checking the directory service event logs I found repeated entries for event ID 13359, stating
It turned out some of the GPOs were missing from the SYSVOL share because it wasn't replicating on the newly virtualized DC. After migrating a standalone Windows domain controller to a VMWare environment, I noticed that some group policy objects weren't being enforced.
