Microsoft's official enterprise support blog for AD DS and more
Ned here again. Today’s post is a quick technique I use to show how to slap the DFS Management snap-in around when it acts foolishly. Hopefully you find it helpful someday.
Here’s the situation
So let’s say I had this:
Then I start up DFSMGMT.MSC and now I have this:
No big deal, I’ll just click the refresh button. Wait, where’s the refresh button? No matter, I’ll just press F5, that always refreshes stuff… crud, still there. Ok, I’ll just press CTRL+A and select everything… you have got to be kidding me! Are you saying that I have to right-click every single object node and choose ‘Remove Replication Group from Display’?
A little background
The DFS UI development team writes the DFS Management snap-in for optimal performance. They achieve performance gains by caching new expensive data from LDAP. This optimization prevents the management tool from over utilizing the network with unnecessary queries. The snap-in recognizes when information is new and remembers it. However, the behavior changes when we delete information. The concept of deleting setting in masses in large environments was overlooked.
Never mind that, fix it!
So where’s this cache? Right here:
Open the path listed above. This path expands to a folder within your profile, like this:
You'll see a file named ‘dfsmgmt’ without a file extension.
Close the DFS Management snap. Then delete or rename the dfsmgmt file. Start the snap-in. Voila. All the extraneous deleted goo, which was removed by someone else, is now gone. You can use the same file and technique to remove large numbers of DFS Roots. We’re looking into getting a darned refresh button added too. ;-)
I told you it was quick.
- Ned ‘Hammer Approach’ Pyle
- Ned ‘Hammer Approach’ Pyle
I had this problem when I was toying with DFSN/DFSR last year...glad to see this technique is documented here now too :)
we notice that when we want to add namespaces with dfsn, only the pdce is used to enumerates dfs namespaces. If the pdce is not online, the enumeration stops with error "domain not found". Is it possible that the DFS Management snap-in uses all DCs but not exclusively the pdce for dfsn enumeration ?
244 Microsoft Team blogs searched, 110 blogs have new articles. 271 new articles found searching from
I've used those cache files for WSUS snapin to get the identical view on both my laptop and desktop machine.
So copying them across machines to supply an initial view is a possibility.
I had started posting some of the interesting Directory Services-related posts from other blogs, but
No, the PDCE must be online for DFS editing to work. If it's offline you should not be worried about DFS, you should be getting it back up! :)
This is very good news was well informed that the followers of the issue I am. Thank you ...
Introducing such a topic you'd like to congratulate you've let us know. Have good work
This and similar information-sharing my vocabulary expanded again. Thank you for your writing ...
I had this problem when I was toying with DFSN/DFSR