I have been tasked to duplicate a folder and have certain users access the copied folder to make changes, however, the changes will not reflect into the originating folder. Is this possible?
Any info would be greatly appreciated.
Yes, take a look @ DFS. Here's a step-by-step configuration guide:
- Proposed as answer by James McIlleceMicrosoft employee Thursday, March 14, 2013 5:31 PM
Thank you for the post.
This issue is related to DFS, we need to create a DFS namespace, add each same folder as folder target and create a replication group as per: http://blogs.technet.com/b/josebda/archive/2009/03/10/the-basics-of-the-windows-server-2008-distributed-file-system-dfs.aspx
Nick Gu - MSFT
At a glance (please correct me if I am wrong) seems that you want to configure something like a one way replication scenario. If you are using Windows Server 2012 or Windows Server 2008 R2, you can create a read-only replicated folder that replicates content through a one-way connection. For more information, see Make a Replicated Folder Read-Only on a Particular Member. It's not supported creating a one-way replication connection with DFS Replication in Windows Server 2008 or Windows Server 2003 R2. Doing so can cause numerous problems including health-check topology errors, staging issues, and problems with the DFS Replication database.
"Why are one-way connections not recommended?
We recommend that customers avoid configuring such one way connections to the extent possible since:
The DFS Replication service’s conflict resolution algorithms are severely hampered if the outbound connection from a member server is deleted (or disabled). Therefore, scenarios where the DFS Replication service is unable to over-write undesired updates occurring on the ‘read-only’ member server with the authoritative contents of the hub/datacenter server may arise.
Accidental deletions on the ‘read-only’ server (in this case, site server ‘design.contoso.com’) could cause issues with the replication updates being trapped on that server. Further, as described above, updates from the authoritative server can potentially not be applied since the parent folder could have been deleted locally. Therefore, with time it is possible to see substantial divergence in the contents of the replicated folders across all replication member servers.
Problems with the deployment are difficult to detect without regular and meticulous monitoring. There might be a lot of false positives in the health report and system eventlogs owing to the fact that the replication topology is being set up to do something DFSR wasn’t designed to handle. Mining through these false positives and monitoring servers can be a challenge.
Administrators need to develop their own scripts to identify which files are backlogged on the ‘read-only’ member (in this case site server ‘design.contoso.com’) and replicate authoritative content back to that ‘read-only’ site server. This can be quite tricky to get right and might need a lot of very close monitoring (perhaps, at times on a per-file basis). Microsoft does not supply any tools for this purpose.
There is a risk of administrators inadvertently creating the missing connection and causing backlogs to flow to and corrupt the contents of an authoritative server. With these changes getting replicated out further from the authoritative server, the contents of the replicated folder could get out of sync and corrupt on all replication member servers very quickly.
Please note that configuring one way connections is not supported by Microsoft Product Support Services."
Using One-Way Connections in DFS Replication: http://blogs.technet.com/b/filecab/archive/2007/08/16/using-one-way-connections-in-dfs-replication.aspx
Another would be to schedule a task to run a script. The script can copy the contents from one server to another.
Also there is a free that can sync folders from one end to another. I have used it before and I can safely recommended and Free!: http://sourceforge.net/projects/freefilesync/
Hope it helps.