After deleting a DFS namespace through the DFS Management snap-in, it may continue to appear on DFS file servers due to inconsistencies in DFS metadata. This can cause confusion, disrupt DFS operations, and make it difficult to manage namespaces effectively.
DFS metadata cache issues: The DFS metadata cache was not refreshed, causing old namespace entries to persist.
Active Directory replication delays: Changes to DFS metadata may not have propagated across all domain controllers, leading to outdated namespace data.
Ensure you have:
Access to DFS Management for verifying and modify namespace deletions.
Permissions to use ADSI Edit to manually remove DFS metadata.
Open DFS Management (dfsmgmt.msc).
Confirm that the namespace no longer exists.
Ensure the deletion was successful and no errors were reported.
Open ADSI Edit (adsiedit.msc).
Connect to the Default Naming Context (domain partition).
Navigate to CN=Dfs-Configuration, CN=System, DC=<your-domain>, DC=<com>
Locate the orphaned namespace entry and delete it.
Restart the DFS service on domain controllers to clear outdated cache:
net stop dfs
net start dfs
This forces DFS to reload its metadata from Active Directory.
Check if changes have propagated to all domain controllers:
repadmin /showrepl
If necessary, force replication using:
repadmin /syncall /AeD
Ensure no replication errors are present.
Attempt to access the deleted namespace from a client machine.
Verify the namespace no longer appears in DFS.
Periodically review DFS metadata to detect orphaned namespaces early.
Changes made in ADSI Edit cannot be undone easily double-check entries before modifying.
Use dfsutil.exe to export namespace configurations before making changes.