I have a branch office opening that needs access to file share we have. The share is \\server1\public.
Our goal is to move this share to DFS, replicate to a server at the branch office, and have the users access the files local to their site all the while keeping the UNC \\server1\public (we have lots of references to the UNC paths in files).
I am aware the File Server Migration Tool with DFS Consolidation Root which seems like exactly what I need. However this only creates a stand-alone namespace on new server (server2). I see that I can replicate the folder using stand-alone namespace to the branch office server. However will all users that reference \\server1\public be only able to hit the new server (server2) which has the consolidated root DFS share or will the stand-alone namespace with replication be able to tell clients at remote site to access the replicated data that resides on their end and not come across to access the share? We are using all 2008 AD and File Servers and have AD Sites set up properly. We are only concerned with moving the one share to DFS and replicate and are not consolidating multiple shares. If there is a better way to approach this I am all ears. Thanks!
Old UNC path: \\server1\public
Consolidated to new DFS: \\Server2\#Server1\Public (Accessible by old UNC)
Replicated offsite to \\RemoteServer3\Public