First, the scenario. I want to use DFS to enable employees in two different sites to share the same files while each accessing a copy that is local (not across the WAN) to them. As I understand it, that's a good thing for DFS to be doing. My question is, however, how does DFS handle file locks? For example:
1. User in Site A opens file X (from his server A's DFS link copy) and makes some edits and sits in the file from 11am to 2 pm while at lunch
2. At 1pm User in Site B opens the same file X through DFS (but using server B's copy). Does this user get a "File is in use" warning??? That's the crux of the issue...
3. Is there a way to shorten the default sync of DFS (which I believe is 15 minutes). When the remote office edits the file on the remote server, we would like to not have to wait 15 minutes to see the changes (assume that our WAN can handle the replication traffic)
4. On machine is Win2003 R2 the other is just Win2003 - I assume I should set up the root on the 2003R2 machine since it has RDC (remote differential compression) which enables only the incremental changes to be be synched. Or do both machines have to be 2003 R2 for that to work?
If anyone has a better thought on how to keep two remote sites in sync and handle concurrent editing issues (short of sharepoint, of course - too expensive), I'm all ears.