Windows 10: Failure to add new DFS namespace

Hi,I would like to add new DFS namespaces but it could not be completed.Could you please help to fix this issue ?Thanks

:)

 

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.

 

Correct way to permanently decommission FS1 without effecting the DFS namespace and replication?

Hi, we are looking to decommission our old DFS file server (FS1). FS1 was the original file server where we setup the DFS and replicated to FS2 and FS3. We had all three servers replicating the correctly
for the past few months. Now we have decided it’s time to decommission FS1. We shutdown FS1 to see if the everything would still function. With FS1 offline, FS2 and FS3 are still replicating without issue.

Can you tell me the correct way to permanently decommission FS1 without effecting the DFS namespace and replication? When I open DFS Management on FS2 I see an error on our namespace. “The namespace cannot
be queried. The specified domain either does not exist or could not be connected”.

Environment: 3 File servers, 1 namespace, 3 replications

FS1 – Server 2008 R2 (Need to decommission but original creator of DFS namespace)

FS2 – Server 2012

FS3 – Server 2012

1 Namespace

\\domain.com\dfs

3 Replications

\\domain.com\dfs\profiles

\\domain.com\dfs\smfiles

\\domain.com\dfs\test

 

DFS Namespaces on Windows7/10

Hopefully someone can help me figure out this issue we are having...

We want to use DFS Namespaces to house files in one central location across all branches, it is setup and working properly at the central office the namespaces are setup at regardless of operating system (windows 7/10). Heres where the confusion comes in,
at all other offices, no one using windows 7 can access the namespaces or the network shares that the namespace replicate from. They will get an arbitrary error saying you dont have permissions to access this, which they do, and when they would go to access
a network share being replicated from it wants a domain login which none work...even a domain admin account will not grant access. Windows 10 users, no problem, they can access everything.
What is windows 10 doing differently than windows 7 to enable this access or where did we go wrong setting up the namespaces?