none
Orphaned DFS Namespace - How to Remove

    Question

  • We have two test namespaces in our domain along with one production namespace.  The two test namespaces had just one namespace server (the hosting file server). That server went down, and we had to rebuild the DFS  configuration.  Now we are stuck with the two test namespaces which show up when we browse for adding namespaces in the DFS Mgmt display, but it gets an "RPC is unavailable" error when I try to explore it.  From a command prompt, running "dfscmd /view \\ourdomain.tld\DFS_Test" results in a "System error 1722 has occurred.  The RPC server is unavailable".  Yet I can query our production one as "dfscmd /view \\ourdomain.tld\DFS_Prod" and it properly shows the DFS folders, so it doesn't exactly sound like a service isn't started or such.

    Any ideas?  I would be happy to simply delete these orphaned Namespaces if I could figure out how!  Thanks!
    Wednesday, February 18, 2009 5:16 PM

Answers

  • Hi WalrusDeveloper,

     

    It seems that you want to know how to delete the orphaned namespace information \\ourdomain.tld\DFS_Test from the DFS Management console. Meanwhile, you can query the current namespace \\ourdomain.tld\DFS_Prod which is on the production server.

     

    As the domain-based DFS configuration stores in the AD database, every time we launch the DFS management console, it will try to retrieve the DFS information from AD.

     

    There are two nodes in AD which stores the information of the DFS:

     

    Node1. Store the DFS Namespace information which shows under the Namespaces node in DFS management console.

     

    CN=DFS-Configuration, CN=System, DC=Domainname, DC=domainsuffix

     

    Node2. Store the DFS Replication group information which shows under the Replication node in DFS management console.

     

    CN=DFSR-GlobalSettings, CN= System, DC=Domainname, DC=domainsuffix

     

    In this case, you may use ADSIedit.msc to delete the orphaned namespace information \\ourdomain.tld\DFS_Test under the node CN=DFS-Configuration.

     

    1. Launch ADSIedit.msc

     

    2. Connect to "Default naming context" (the domain partition)

     

    3. Expand and locate to the following node:

     

    CN=Dfs-Configuration, CN=System, DC=ourdomain, DC=tld

     

    4. Check if the orphaned namespace CN=DFS_Test is under it, if so, you may delete this node CN=DFS_Test

     

    Afterwards, please run "repadmin /syncall" if there is multiple domain controllers in the environment and then run "dfsrdiag pollad" on all the DFS member servers to manually make them sync the information from AD database.

     

    Then, you may launch the DFS management console and then right-click on the orphaned namespace, and then select Remove Namespace from Display… if needed.

     

    Hope it helps.


    David Shen - MSFT
    • Marked as answer by David Shen Saturday, February 21, 2009 7:39 AM
    Thursday, February 19, 2009 7:49 AM

All replies

  • Hi WalrusDeveloper,

     

    It seems that you want to know how to delete the orphaned namespace information \\ourdomain.tld\DFS_Test from the DFS Management console. Meanwhile, you can query the current namespace \\ourdomain.tld\DFS_Prod which is on the production server.

     

    As the domain-based DFS configuration stores in the AD database, every time we launch the DFS management console, it will try to retrieve the DFS information from AD.

     

    There are two nodes in AD which stores the information of the DFS:

     

    Node1. Store the DFS Namespace information which shows under the Namespaces node in DFS management console.

     

    CN=DFS-Configuration, CN=System, DC=Domainname, DC=domainsuffix

     

    Node2. Store the DFS Replication group information which shows under the Replication node in DFS management console.

     

    CN=DFSR-GlobalSettings, CN= System, DC=Domainname, DC=domainsuffix

     

    In this case, you may use ADSIedit.msc to delete the orphaned namespace information \\ourdomain.tld\DFS_Test under the node CN=DFS-Configuration.

     

    1. Launch ADSIedit.msc

     

    2. Connect to "Default naming context" (the domain partition)

     

    3. Expand and locate to the following node:

     

    CN=Dfs-Configuration, CN=System, DC=ourdomain, DC=tld

     

    4. Check if the orphaned namespace CN=DFS_Test is under it, if so, you may delete this node CN=DFS_Test

     

    Afterwards, please run "repadmin /syncall" if there is multiple domain controllers in the environment and then run "dfsrdiag pollad" on all the DFS member servers to manually make them sync the information from AD database.

     

    Then, you may launch the DFS management console and then right-click on the orphaned namespace, and then select Remove Namespace from Display… if needed.

     

    Hope it helps.


    David Shen - MSFT
    • Marked as answer by David Shen Saturday, February 21, 2009 7:39 AM
    Thursday, February 19, 2009 7:49 AM
  • This worked like a charm!  Many thanks!

    Sorry about the delay in responding - other work items pre-empted this for a time....  Thanks again!
    • Proposed as answer by JC Pirmolin Wednesday, July 15, 2015 8:40 AM
    Wednesday, March 04, 2009 9:59 PM
  • This worked for us as well. One slight difference, we reinstalled the server that had been hosting the namespace to Server 2008 R2 and before we could re-add the namespace to the server it required a reboot. Even after dfsrdiag pollad the server still thought that a server with it's name already had that namespace.
    Monday, March 08, 2010 5:08 PM
  • I just googled "Problem removing a DFS Namespace" and your answer was at the top of the list. Your advise solved my problem.

    Thank you so very much.

    Saturday, July 21, 2012 11:13 PM
  • I ran into the same problem, and eventually is was fixed.

    Please consider writing a KB article on this problem - it is likely to be confronted by others.  When you do,  please consider changing the lines as follows to be consistent with the tree display in ADSIedit:

    CN=DFS-Configuration, CN=System, DC=Domainname, DC=domainsuffix

    to

     CN=System, CN=DFS-Configuration,, DC=Domainname, DC=domainsuffi

    and

    CN= SystemCN=DFSR-GlobalSettings,  DC=Domainname, DC=domainsuffix

    to 

    CN=DFSR-GlobalSettings, CN= System, DC=Domainname, DC=domainsuffix

    Tuesday, June 25, 2013 9:20 PM
  • Please do edit your great post with the changes suggested by dbaum22101, I was head scratching until I read down the thread
    Wednesday, September 25, 2013 2:35 PM
  • You can delete an orphaned dfs namespace server launching this command.

    dfsutil diag unmapdomroot  \\ourdomain.tld\DFS_Prod \\server_to_remove\namespace

    Regards.

    Tuesday, December 13, 2016 11:59 AM
  • HELP: ADSIedit is not found on Windows Server 2012-R2.

    Anyone know how to get this loaded on Server 2012R2 ?

    Regards,

    Mike

    Saturday, July 15, 2017 6:12 PM
  • HELP: ADSIedit is not found on Windows Server 2012-R2.

    Anyone know how to get this loaded on Server 2012R2 ?

    Regards,

    Mike


    Install the RSAT/AD Tools feature to get ADSIedit. You don't need to add the AD Role, only the tools feature

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Sunday, July 16, 2017 7:17 AM