Orphaned DFS, can't remove

Question

At some point in the past a customer must have toyed with DFS then abandoned it (they're not currently using it across any of their 4 servers).  We're now preparing to deploy DFS Namespaces and after DFS was installed on their new Server 2022 system (all the servers at this company are Server 2022) an old DFS share showed up:

 

\domain.local\profiles (appears to be a Server 2008 mode Domain-based namespare)

 

Clicking on it gives me the RPC Server not found.  I can "hide" it but it says it'll still be available, but since it doesn't work it really should be deleted to avoid confusion down the road.

 

I can only assume they toyed with doing roaming profiles or something in the past.  The Namespace doesn't exist when I attempt to browse to it and when it use ASDIEdit (as described here: https://social.technet.microsoft.com/Forums/ie/en-US/2463ce92-7767-4135-b8c7-31c736bdabc2/orphaned-d...) where I would normally see the orphaned Namespace it's not there.

EDIT: To clarify, the link in the last paragraph does no good because there is only one entry in ASDIEdit for CN-DFS...... and it's not what they said would be there:

As you can see, this is sorted alphabetically yet there is only one CN=Dfs and it's for -Configuration not the missing namespace which is:

\domain.local\profiles:

Anyway, any thoughts on where/how I find this Namespace so I can remove it or do you think I can go down the road of recreating it using the exact same spelling and then delete it?

Thanks!

Answer 1

Normally, you should be able to see something in ADSIEdit...

Answer 2

This may help you

https://social.technet.microsoft.com/Forums/ie/en-US/2463ce92-7767-4135-b8c7-31c736bdabc2/orphaned-dfs-namespace-how-to-remove?forum=winserverfiles