I've been having some issues with our DFS setups with both file replication with Roaming Profiles and with Folder Redirection. Also it appears that though I have 2 servers setup for replication (DC1 & DC0) if DC1 goes offline the DFS is not available even thought the files are replicated on to DC0.
First I'll start with the file replication errors. I've been having issues with NTUSER.DAT files being replicated. Since then I've disabled Offline file caching on the share since I read that can cause issues. Also there appears to be some errors with some files (8 files) that are in a users folder that is being redirected. Is there anyway to retry the replication of these files to see if the issue is gone? I've ran the DFS health report and the files are still showing up with errors.
Second, for the longest time we've had only one server in DFS. I wanted to make the DFS available if the server were to go offline so I added a second server to the DFS group. The first original server DC1 is windows 2003 R2 with iSCSI to our NAS. I since added another NAS and connected it with iSCSI to a second server, DC0 (win 2008r2). File replication is working in both directions aside from the few file errors I mentioned above. The problem is if the original server DC1 goes offline, DC0 doesn't serve the DFS at the //domain.dom/dfs namespace as I would expect it would?
Is this a configuration issue?
Thank you!