Dfs main folder got renamed automatically to gibberish (on 3 servers)

DFS - server 2012.  I set up 3 new servers and added them into dfs.  Everything was fine for a few days until the servers got rebooted.  (I assume it was the servers rebooting that did this)

our main dfs folder   E:\Shares\DFS\Source
got renamed to this   E:\Shares\DFS\DFS.6f991b56-b1e6-4ace-9a5d-b09fb3c82417Source
so the dfs path everyone is using is broken.
and also now in E:\Shares\DFS\  there's a shortcut it looks like, called source.  and when I try to open it, it says inaccessible.

I'm not finding anything in the eventlogs other than dfs complaining that the path is no good now.
So what did windows do.  Did it say,  I want to put a source shortcut there, but there's already a folder there named source, so lets rename the folder, and put a source shortcut there?
Is that source shortcut susposed to even exist if the actual folder is already at that location?  I notice our older dfs servers have a C:\DFSRoots folder that contains that shortcut looking icon.  Not on the new servers though, as I directed them to use the location of the main folder.  Could anyone provide some insight?  thanks
JohnPaddockAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

efrimpolCommented:
Not a fan of DFS, although I can see the merits.

One thing I've learned over the years, that if something breaks (software-speaking), first thing I ask myself is "Do I have a backup?".

If I don't, then i blame myself for not having one, start backing up data elsewhere and start taking a different route in troubleshooting.

If I do, then I kind of start taking things apart and put them back together.

That's what i would suggest with DFS. Remove it, making sure all the data is there, and reestablish it.
0
efrimpolCommented:
Just to be sure, I am only stipulating that you further examine what is going on, and IF you need to rebuild DFS, please make sure you have current backups and if you don't, make them before going any further.
0
JohnPaddockAuthor Commented:
So it appears that the issue was that I directed the namespace to use the same folder as the replication folder.  Namespace and replication are 2 separate things, and should be in separate folder structures.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
efrimpolCommented:
Some times, its the little things...
0
JohnPaddockAuthor Commented:
solved
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.