Hi,
We currently have two DFS servers. The original member server at our site is a Server 2003 Standard (x86), and the new (replacement) server is a virtual Server 2008 R2 Standard (x64) on a Hyper-V host.
I brought the new server online, added the DFS role and added it a a replication member. Once everything had replicated across the to the new server, I started disabling the old '03 member machine and deleting it as a replication member server from within the DFS Management Console. For the most part, it has worked perfectly fine. There are however a few replication groups in the various namespaces that list the old '03 server in the DFS tab, and for some reason it takes a few minutes to open those folders from the namespace - it's almost as if it's still looking for that old member server (which has currently been disconnected from the network), can't find it, so it looks to the new server after a minute or two and opens the folder immediately. There are however other folders in the namespace that don't have the old server listed in the DFS tab, and they open without any delay as a result.
I used this methodology of retiring the old DFS server based on my own logic. I haven't been able to find any sort of "step by step" procedure on how to retire an old DFS server. Firstly, has the method I used been effective enough? Secondly, how can I remove references to that old DFS server to correct this "lag"?