Windows 10: DFS cache issue

We have a domain which has 6 different sites, 3 of the sites has a DC and a DFS server. To make this easier to see:Site A: DC + DFS + PCsSite B: DC + DFS + PCsSite C: DC +DFS + PCsSite D: just PCs, all PCs point DNS to site A plus DFSSite E: just PCS all PCs point DNS to site A plus DFSSite F: just PCs all PCs point DNS to site A plus DFS. All PCs all windows 10 in the entire network got built at site A then physically installed at each site. The DFS issue is that we have 2 shares Share A and Share B that get pushed out via gpo to all users and all sites and PCs. The issue is Share A and B b

:)

 

Microsoft DFS Folder Access Issue

Hi,

I am migrating DFS name space from Windows 2003 to Windows 2016 in Stand alone DFS with Cluster Environment.

I am facing issue that after creating DFS name space role in windows 2016 that Folder - Folder access through \\DFSNameSpace\Shared Folder\DFS links or Shares

I am expecting that DFS Name space can be accessed like \\DFSNameSpace\DFS links or Shares. This way I am able to access in windows 2003.

 

how to sync dfs namespace server into work folders??

we have data in DFS name space server, we need to sync DFS server with work folder, how to integrate DFS to work folder?? if its possible suggest the way to do it.

 

DFS Namespace issue

I've got an issue with network shares containing shortcuts of themselves. This creates and endless loop when searching, among other issues. When attempting to delete the shortcuts, I would receive errors. Using fsutil i was able to find that these shortcuts
are DFS Reparsepoints, and also was able to remove the reparsepoints and delete the folders (article). But they
kept coming back.

It took a really long time, but I finally figured out that each of the shares with this issue has a DFS Namespace set up, and I believe that the issue is how the targets were created. For instance the shares with this problem exist as such: \\Server1\Share1
and \\Server2\Share1 (these are replicated to each other). The namespace is listed as \\DomainName\Share but its namespace path is \\DomainName\Share1\Share1. I believe this is causing the namespace to create this reparsepoint INSIDE the share instead of
AS the share.

I hope this isn't coming across as gibberish. How do I fix this? I can't simply edit the namespace path, and I'm afraid deleting the namespace itself will break everything.