DFS won't replicate onto two volumes on a server but works on C:

[Pete88]

Weird situation for you.

 

4 Servers.

 

DFS works on 3 servers

 

DFS sort of works on the remaining 1 server, but not in the way that we want. If I add the server as member to the replication group using a local path on the C:\ drive, it works no problems, the health report shows no issues and replication happens full circle between all of the members servers, If however I use our J volume, which is a brand new 5TB volume (absolutely crucial that this volume is included in our DFS setup), no joy, this also happens on our G volume which was our old storage array.

 

I get no event log messages explaining why this is the case, the only clue I have is the DFS health report. When using a folder on the C volume, the health reports lists the C drive as a volume where replicated folders exist, no errors or warnings. When using the G or J volumes, the DFS health report gives back no errors as before, but it also doesn't list the G or J volumes (it does this fine for the other working servers), it still lists the C volume because of the sysvol folder living there.

 

When attempting the use this problematic server as the primary designated member, the DFS health reports states: "Reference member returned no replicated folders.

Description: Backlog calculations cannot be performed because the reference member returned zero replicated folders" - almost as if it can't see or recognise the folder targets I added into the replication group.

 

I've searched high and low for a solution to this but to no avail. I was hoping someone else in the education sector may have come across it.

[Pete88]

No-one come across this..?