This deserves an award for weird!
We’re running Windows Server 2008 R2 on multiple virtual servers using DFSR to replicate folders. And all is well except for one folder that’s not replicating. This folder used to be a high level folder directly on the root of a drive but was later moved under another replicated folder. I searched for issues such as this and found a very interesting article that applied to Windows Server 2003 that matched my problem (KB 948833). However, I haven’t found anything that stipulates Server 2008 R2.
OK. So I decided to do a manual copy. That’s when the fun started. From the source server, I selected the source folder and then selected the destination server/directory and said copy. To my surprise, the system came back and said it found existing folders there, do I wish to replace them. I looked again at the destination folder and they didn’t show there, and there were no filters in place to hide them. So I cancelled the copy operation and said, let me create the folder on the destination server. Right clicking within the directory on the destination server, I said Create Folder, and gave it the name I desired. To my surprise, it kept the name New Folder. Thinking I had fat fingered it, I attempted to rename that folder once again to the desired name only to get the same result.
It appears that the destination system is aware of the folder that can’t be seen. However, if I attempt to use Windows Explorer to pull up that folder, it can’t find it. So, how can I “see” this folder, replicate it or remove it? Are there some DFSRDIAG commands I can use to reveal what’s going on under the covers? The Server Manager console interface doesn’t show any replication for the folder that was once a high level folder and the folder that now contains that subfolder is being replicated properly except for the desired subfolder. And there are no errors present in the event viewer. Any ideas? How about an award for this weird one!!