DFS Namespace Server - Member or DC?

Discussion in 'File Systems' started by MarkA, Sep 12, 2008.

  1. MarkA

    MarkA Guest

    Is it better to configure member servers, or DC's as DFS W2K8 (Native Mode)
    DFS Namespace servers?

    I am in conflict with a colleague who is intent on using DC's, however my
    preference is to install the DFS Services (incl DFS Namespaces & DFS
    Replication services) on member server F&P servers, rather than DC's....

    Any recommendations, suggestions greatly appreciated!
    MarkA, Sep 12, 2008
    #1
    1. Advertising

  2. MarkA

    DaveMills Guest

    Personally I go with you because a) I like to keep DC uncluttered b) DFS is a
    File service so it seems logical to have it on a file server.


    On Thu, 11 Sep 2008 22:55:01 -0700, MarkA <>
    wrote:

    >Is it better to configure member servers, or DC's as DFS W2K8 (Native Mode)
    >DFS Namespace servers?
    >
    >I am in conflict with a colleague who is intent on using DC's, however my
    >preference is to install the DFS Services (incl DFS Namespaces & DFS
    >Replication services) on member server F&P servers, rather than DC's....
    >
    >Any recommendations, suggestions greatly appreciated!

    --
    Dave Mills
    There are 10 type of people, those that understand binary and those that don't.
    DaveMills, Sep 12, 2008
    #2
    1. Advertising

  3. Hi,

    In my vew, DFS root should be on Domain Controller and DFS Link should be on
    file share (May be clustered)


    "DaveMills" wrote:

    > Personally I go with you because a) I like to keep DC uncluttered b) DFS is a
    > File service so it seems logical to have it on a file server.
    >
    >
    > On Thu, 11 Sep 2008 22:55:01 -0700, MarkA <>
    > wrote:
    >
    > >Is it better to configure member servers, or DC's as DFS W2K8 (Native Mode)
    > >DFS Namespace servers?
    > >
    > >I am in conflict with a colleague who is intent on using DC's, however my
    > >preference is to install the DFS Services (incl DFS Namespaces & DFS
    > >Replication services) on member server F&P servers, rather than DC's....
    > >
    > >Any recommendations, suggestions greatly appreciated!

    > --
    > Dave Mills
    > There are 10 type of people, those that understand binary and those that don't.
    >
    Vipin Chhabra, Sep 18, 2008
    #3
  4. MarkA

    DevilsPGD Guest

    In message <> Vipin
    Chhabra <> wrote:

    >In my vew, DFS root should be on Domain Controller and DFS Link should be on
    >file share (May be clustered)


    We're doing the same here, although I can't say I'm thrilled about it.

    Our logic is that this way all a user needs to know is \\domain.name and
    they can use that same name for anything from authentication (obviously
    with their own name as well), email, VPN, to accessing files.

    Since DCs need to be file servers as well for the default AD share,
    there doesn't seem to be much harm in having a DFS root there too.
    DevilsPGD, Sep 18, 2008
    #4
  5. Hello,

    From the DFS perspective, there's no difference between creating a DFS root
    in a member server or a DC.


    "DevilsPGD" wrote:

    > In message <> Vipin
    > Chhabra <> wrote:
    >
    > >In my vew, DFS root should be on Domain Controller and DFS Link should be on
    > >file share (May be clustered)

    >
    > We're doing the same here, although I can't say I'm thrilled about it.
    >
    > Our logic is that this way all a user needs to know is \\domain.name and
    > they can use that same name for anything from authentication (obviously
    > with their own name as well), email, VPN, to accessing files.
    >
    > Since DCs need to be file servers as well for the default AD share,
    > there doesn't seem to be much harm in having a DFS root there too.
    >
    John Angel [MSFT], Sep 27, 2008
    #5
  6. MarkA

    DevilsPGD Guest

    In message <> John
    Angel [MSFT] <> wrote:

    >From the DFS perspective, there's no difference between creating a DFS root
    >in a member server or a DC.


    True, but from a user experience point of view, it's very different.

    If the DFS root is replicated to all DCs, then as long as any one DC is
    up, \\domain.lan\dfsroot is all the user needs to know to access files,
    whereas if the root is hosted on a specific server (or even set of
    servers), the user needs to guess which server is local and available.
    DevilsPGD, Sep 27, 2008
    #6
  7. MarkA

    DaveMills Guest

    On Sat, 27 Sep 2008 09:47:38 -0600, DevilsPGD <>
    wrote:

    >In message <> John
    >Angel [MSFT] <> wrote:
    >
    >>From the DFS perspective, there's no difference between creating a DFS root
    >>in a member server or a DC.

    >
    >True, but from a user experience point of view, it's very different.
    >
    >If the DFS root is replicated to all DCs, then as long as any one DC is
    >up, \\domain.lan\dfsroot is all the user needs to know to access files,
    >whereas if the root is hosted on a specific server (or even set of
    >servers), the user needs to guess which server is local and available.


    Why?
    My DFS root servers are all member servers and \\domain\root works fine. The
    only time I need \\server\root is if the PC is not a domain member.

    --
    Dave Mills
    There are 10 types of people, those that understand binary and those that don't.
    DaveMills, Sep 28, 2008
    #7
  8. MarkA

    Maximilian Guest

    You can create Namespaces on \\Server1 and \\Server2. This will provide
    redundancy for the namespaces.

    Your targets to let's say \\domain.com\DFS will be \\Server1\DFS and
    \\Server2\DFS.

    You will direct your users to always use \\domain.com\DFS and NEVER EVER use
    the server names. As I've directed mine. They will never have to worry about
    server names where the Namespaces or actual files are hosted, keeping you
    free to move your data around.
    --
    _______________
    Maximilian


    "DevilsPGD" wrote:

    > In message <> John
    > Angel [MSFT] <> wrote:
    >
    > >From the DFS perspective, there's no difference between creating a DFS root
    > >in a member server or a DC.

    >
    > True, but from a user experience point of view, it's very different.
    >
    > If the DFS root is replicated to all DCs, then as long as any one DC is
    > up, \\domain.lan\dfsroot is all the user needs to know to access files,
    > whereas if the root is hosted on a specific server (or even set of
    > servers), the user needs to guess which server is local and available.
    >
    Maximilian, Sep 29, 2008
    #8
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Chris Meehan
    Replies:
    5
    Views:
    368
    Isaac Oben [MCITP,MCSE]
    Mar 27, 2009
  2. Adam Sudol
    Replies:
    4
    Views:
    1,975
    Dan Lovinger [MSFT]
    Jul 6, 2004
  3. okey
    Replies:
    3
    Views:
    565
    Jill Zoeller [MSFT]
    Oct 16, 2006
  4. Richard P
    Replies:
    1
    Views:
    943
    Richard P
    Apr 15, 2007
  5. BH337
    Replies:
    0
    Views:
    845
    BH337
    Mar 4, 2010
Loading...

Share This Page