This questions is specific to Server 2008 R2.
Everyone has seen the 4302 event; "The DFS Replication service has been repeatedly prevented from replicating a file due to consistent sharing violations encountered on the file".
What happens in this scenario: someone opens a spreadsheet on Server-A. At some point while that file is open, replication is attempted. The 4302 is thrown. The file is not replicated. At that same point in time someone opens that same file on Server-B. Those two DFS folders are configured to replicate. The user working from Server-B attempts to make changes to that spreadsheet. Does he/she get a warning message saying the file is in use? I don't believe so, since we're talking about a file on a different server. Both users make changes at the same time, to the same file. There's no way DFS-R can correctly sort that out. Someone's changes are going to be lost.
Have you experienced this scenario?
And if so, how did you avoid it going forward?