Post by Dave Warren Post by DaveMills Post by Jim
I know it is recommended to use your Domain Controllers as the Namespace
I don't recall ever seeing such a recommendation but it does publish the DFS
root to the browser list.
Isn't this basically a requirement to avoid having a single point of
failure in the DFS root unless you run Enterprise across the board and
make use of clustering?
No you only need multiple DCs and multiple DFS Root servers but see my comments
Post by Dave Warren
In other words, unless you use DCs, users need to guess which DFS root
is both local to them (and up right now) in order to access any other
resources under the DFS shares.
I might be wrong about that, when we rolled out DFS we didn't have
enough servers to have any other options and it would take a lot to
According the "How DFS Works"
having the DFS service installed on a DC is now part of the "optimal
I think this has changed since I first read this document. Clearly from "How DFS
works" you do not have to have the DFS service on all DCs but maybe it helps to
do so. The client will get the root referral to the DC instead of a DFSRoot
server. This could be less demanding on the client as it already has a
connection to the DC. It may also help resolve the long delays that occurs when
a DFS Root server goes down.
I will have to review my configuration and look into adding the DFS Server role
to the DCs.
There are 10 types of people, those that understand binary and those that don't.