I setup a new Windows 2012 file server several months ago. I installed the DFS role as we planed to use DFS to replicate the file data to a second file server later. It's been a while since I used DFS and for some reason (not sure what I was thinking) I created a share named 'CompanyData' within the DFSRoots folder? I then created a DFS Namespace, also named 'CompanyData'. I cant remember why I did this but I guess at the time I forgot how DFS works. Users have been successfully accessing data using \\domain.local\companydata for several months now. We have just setup a second W2k12 file server with the DFS role. I have added the new server to the CompanyData namespace. I've just realised I never actually added a folder to the namespace. When I try to add the folder CompanyData it's accessible address becomes \\domain.local\companydata\companydata. My problem is I have users with mapped drives, shortcuts, gpo's etc which are all pointing to \\domain.local\companydata. What would be the least painless way to correct this?

Hi,

So the DFS namespace \\domain.local\companydata is directly point to  c:\DFSroots\companydata. Which means actually users are accessing a shared folder instead of a DFS namespace. Is this correct?

If you would like to use a regular namespace name, like \\domain.local\root\companydata, it is better to create it and config it from start. Change user mapping to the new namespace. It will just take some time until use forget the old folder.

Or, as you said, create \\domain.local\companydata\companydata, and move c:\DFSroots\companydata out of c:\DFSroots. Users will notice that there is one more level until they can see the content.

If this is acceptable, I think following steps should help:

1. Run a Robocopy /copyall c:\DFSroots\companydata x:\companydata to copy all files to x:\companydata

2. Add your second server to DFS namespace and replication group. Do a rbocopy too as a pre-staging.

3. Wait for the initial replication to be finished. 

4. Delete your ServerA from the folder target.

5. Add the new folder x:\companydata back as a folder target. 

Yes exactly. Not sure what i was thinking at the time but as a result users are accessing a shared folder within C:\DFSRoots\CompanyData. Because I put the CompanyData share inside the DFSRoot folder it's accessible via \\domain.local\CompanyData... dooooh!

 I was thinking of the following steps during a maintenance window:

 - Un-share and move the companydata folder out of C:\DFSRoots to C:\companydata and reshare (ntfs permissions shouldn't be effected?)
 - Delete old dfs namespace and create new one as you suggested (\\domain.local\root)
 - Add both file servers to namespace and setup replication group
 - Add companydata as target folder
 - Update gpos, mapped drives, shortcuts, etc so users are redirected to the new dfs path \\domain.local\root\companydata

Many thanks for your advice Shaon. Can you see any issues with the above?

Steps are OK. And you can copy files with NTFS permissions by using Robocopy.