migrate from standalone DFS to domain DFS

Discussion in 'File Systems' started by Guest, Oct 16, 2006.

  1. Guest

    Guest Guest

    I have a customer who have a Windows 2000 cluster containing standalone DFS.
    The servers are getting old and they want to migrate to domain based dfs and
    R2 server - and no clustering.
    They have knowledge about most stuff but asked me about migrating the
    standalone root to domain based root.
    My first thought was to "DisableStrictNameChecking"
    (support.microsoft.com/kb/281308) and leave it at that, but since the dfs
    root will be located on DCs I just have to check with you guys first.



    Or is there a better way to migrate from standalone DFS to domain DFS?
     
    Guest, Oct 16, 2006
    #1
    1. Advertisements

  2. Guest

    Guest Guest

    Dude, that really wasn't an answer to the question...

    We will throw away the old 2000 cluster and replace it with new 2003 R2
    servers. There will be no need to replicate the data, we can do a
    backup/restore or robocopy or something when we migrate.

    The question was regarding the "DisableStrictNameChecking" on the DC's that
    will host the DFS root so that we don't have to edit all users connections
    to the DFS namspace...




    Nope. R2 can only replicate with other R2 machines (or Longhorn... someday).

    --
    Ned Pyle
    Microsoft Enterprise Platforms Support

    All postings on this newsgroup are provided "AS IS" with no warranties, and
    confer no rights.
    For more information please visit
    http://www.microsoft.com/info/cpyright.mspx to find terms of use.
     
    Guest, Oct 16, 2006
    #2
    1. Advertisements

  3. Guest

    Guest Guest

    I'm glad to see that more people than me are a bit confused at times ;)



    There are some connections from user clients that are connected trough
    mapped drives, sadly not everything. In some documents hyperlinks are unc
    and in some cases <driveletter>\path. There is also some server systems
    dropping files to the dfs and this is done trough unc paths.



    My guess is that we have to create the new dfs root on the new servers and
    do a step-by-step migration of data and not the one-shot I was hoping for.
    User-data and system-data are fairly separated but it still we be some work
    to get everything running smooth again.



    Thanks Ned!





    /Fred


    It would have if I had replied to the correct post. ;-)

    Setting DisableStrictNameChecking on a DC will lead to duplicate name errors
    on the network, if I recall. Bottom line, you are going to have do some user
    behavior modification here. FSMT does not support moving from standalone to
    domain-based DFS, or I'd point you that way. We don't have an easy mechanism
    to do what you're describing (although you can can use DFSUTIl to at least
    export the current link target info for an easier deployment going forward).

    I'm sure they don't as this would be too easy, but do the users connect to
    current stuff via mapped drives?

    --
    Ned Pyle
    Microsoft Enterprise Platforms Support

    All postings on this newsgroup are provided "AS IS" with no warranties, and
    confer no rights.
    For more information please visit
    http://www.microsoft.com/info/cpyright.mspx to find terms of use.
     
    Guest, Oct 17, 2006
    #3
    1. Advertisements

Ask a Question

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

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.