Windows 2003 R2 DFS/FRS backward compatibility

Discussion in 'File Systems' started by Joe H, Sep 19, 2006.

  1. Joe H

    Joe H Guest

    We currently have a number of Windows 2000 servers running DFS in our Windows
    2003 domain. We'd like to replace one of the 2000 servers with one running
    Windows 2003 R2. I know there have been some changes to the way DFS works in
    R2, so is it backwards compatible with Windows 2000 DFS? If so, is there any
    info you can point me to in regards to this?

    Thanks,
    Joe
     
    Joe H, Sep 19, 2006
    #1
    1. Advertisements

  2. It depends on what you mean by "DFS." Are you talking about a namespace, or
    do you mean FRS replication? For namespaces, the DFS service has
    enhancements in R2 but still works fine in a mixed OS server environment.
    There is also a nice new snap-in (aka DFS Management) for managing your
    namespaces.

    If you're talking about FRS, then you can still run FRS on your R2 server,
    but you'll need to manage this using the previous version of the snap-in,
    called Distributed File System snap-in. R2 includes a great new replicator
    called DFS Replication, but this works only on R2 servers.

    I'm pasting some text in below that discusses the namespace interop
    considerations.

    It is possible to use DFS Namespaces when domain controllers and namespace
    servers run a mix of Windows 2000 Server, Windows Server 2003 with SP1, and
    Windows Server 2003 without SP1, but some functionality is disabled or
    available inconsistently, depending on the operating systems on the servers.
    Some examples of mixed-mode behavior are as follows:
    . If domain controllers or namespace servers are running Windows
    Server 2003 without SP1, they cannot provide referrals that support target
    priority or client failback.

    . If domain controllers or namespace servers are running Windows 2000
    Server, they cannot provide referrals that support target server priority or
    client failback, nor can they order targets by lowest cost in referrals.
    Additional configuration is required to enable these namespace servers and
    domain controllers to detect the site of each target server in the
    namespace. For details, see the answer to the question "What are the issues
    to consider when I use multiple servers running Windows 2000 Server and
    Windows Server 2003 to host a domain-based DFS root?" in the DFS FAQ on the
    Microsoft Web site at http://go.microsoft.com/fwlink/?LinkId=39465.

    . If the DFS Management snap-in connects to a namespace server that is
    not running Windows Server 2003 SP1 or Windows Server 2003 R2, none of the
    new configuration settings (such as client failback and target priority) can
    be enabled. Renaming or moving folders will not work, and delegation will
    not be effective.
     
    Jill Zoeller [MSFT], Sep 19, 2006
    #2
    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.