Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're migrating the main media store for our website to a new server. I'm investigating using distributed file system (DFS) to do this, so that instead of replacing all the hard-coded references to \\oldserver\media with \\newserver\media in our website code and config files, I can:

  1. Set up \\\dfs as a DFS share
  2. Add a media folder to that DFS share, with a target pointing at \\oldserver\media
  3. Update all my code and config files to use \\\dfs\media instead of \\oldserver\media

and then when that's all done, add a DFS target of \\newserver\media\, remove the \\oldserver\media target, and (theoretically?) my web servers will then start finding the new server instead of the old one when following that media share.

Nice theory. Doesn't work. Right now, if I go to \\\dfs\media from my workstation in Windows Explorer, I can see the NEW server (which is correct), but virtual directories in IIS that are mapped to \\\dfs\media are still seeing content on the OLD server.

What's bizarre is that the DFS configuration on the domain controller doesn't even have a reference to the old server any more - I've removed the target, and done a dfsutil cache domain flush and dfsutil cache referral flush on my workstation.

Is my local machine maintaining a separate referral cache that's used by IIS but not by Windows Explorer? Is there some other resolution mechanism that could explain why different processes on the same host are seeing different results?

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.