How do I configure a Distributed File System (DFS)?

Windows Distributed File System allows users to find, view, and work with files on your network from one central location. In this tutorial, we will simplify how to work through this difficult configuration.

A Windows Distributed File System (DFS) allows users to find, view, and work with files on your network from one central location. With DFS configured, users do not have to understand the complexities of a network or enter long UNC addresses to browse to files. DFS is installed with Windows 2000 Server, and the service starts automatically. Let’s see how you can take advantage of this great new feature.

Selecting a DFS configuration

There are two types of DFS systems: standalone and fault tolerant. A standalone DFS system stores information on one server. The drawback to this kind of setup is that if the server fails, your DFS goes down. A fault tolerant system stores the DFS information in Active Directory (AD). This type of system gives you replication and fault tolerance.

Creating a DFS root

Before you can access any DFS shares, you must first create a DFS root. The DFS root object stores all the links to your shares and files. I think of the DFS root as an empty container that holds links to all of my shared folders spread throughout my network. Before creating your DFS root, compile a list of all network shares on your system. This helps when the time comes for setting up DFS links, which we’ll discuss later in this article.

To create a DFS Root:

  1. From the Start menu, select Administrative Tools | Distributed File System to access the Microsoft Management Console shown in Figure A.
  2. Right-click on the Distributed File System and select New DFS Root to launch the New DFS Root Wizard.
  3. Click Next and select the type of DFS root you want to create from the screen shown in Figure B.
  4. Select the Domain and click Next.
  5. Enter the fully qualified domain name (FQDN) of the host server, as shown in Figure C, and then click Next.
  6. Select a DFS root share from the screen shown in Figure D and click Next.
  7. Click Next and then click Finish, and you’ll see something similar to Figure E.

After you create the DFS root, you can check the status of the installation by right-clicking on your DFS root and selecting Check Status, as shown in Figure F. If you have configured the DFS root properly, you’ll see a green checkmark inside a circle.

Now that you have configured your DFS root, you’re ready to create links to your shared folders that are located throughout your network. Follow these steps to create the DFS links:

  1. Right-click on your DFS root and select New DFS Link.
  2. Enter the name of the DFS link.
  3. Browse your network to the shared folder, as we’ve done in Figure G, and click OK.
  4. Right-click on the new link and choose Check Status. Again, you’ll want to look for the green check mark inside the white circle to verify that it is running (Figure H).

After establishing your links to the desired shared files on your network, you will want to publish the shares in Active Directory.

To publish a share in AD:

  1. Select Active Directory Users And Computers from the Administrative Tools folder. Right-click on your domain and choose New | Shared Folder.
  2. Enter the name and network path to the DFS share, as shown in Figure I, and click OK.

Now that you have published your share in AD, you can have users view the share by either mapping a drive or by choosing My Network Places | Entire Network | View Entire Contents | Directory | The name of your share (ACME Corporation, in our example) as seen in Figure J and Figure K.


Replication allows you to share folders and DFS links to other DFS roots in a domain. It also provides excellent fault tolerance in case a server crashes or has to be rebooted. You can replicate on a DFS shared folder or a DFS root.

The most important aspect of DFS is the DFS root. I say this because if the DFS root goes down or crashes and you do not have replication of the DFS root configured, your DFS tree is inaccessible.

To configure replication for the DFS root, right-click on the DFS Root and select New Root Replica. You will then need to enter the name of the server you want to copy the root to. To set the replication policy:

  1. Open DFS from the Administrative Tools folder.
  2. Right-click on a link and choose New Replica to open the Add A New Replica dialog box, shown in Figure L.

DFS replicates files every 15 minutes on NTFS partitions; you must manually replicate Fat32 partitions.

I hope I have explained the basics of configuring a DFS root, creating links, and configuring replication. DFS can simplify your job as net admin. You won’t have to worry about entering long UNC paths or creating a bunch of drive mappings by hand (or in logon scripts) for each computer and/or user. DFS is easy to set up and manage, and it provides you with one central location for all shared files on your network.


Hi, I have Windows 2003 Server R2 on Servers and Windows Xp Pro , Windows 2000 Pro on Clients. I have installed a PDC(Primary Domain Controller) ? Let?s call it as DC1 I have installed a Second DC using (Additional Domain Controller for an existing domain controller option) ? Let?s call it as DC2. I have Configured Domain Based DFS on PDC ( ROOT and Links) and ADC (ROOT TARGET and Link Targets). Please tell me: 1) If DC1(PDC) goes down, will DC2 (ADC) take over automatically i.e fail over mechanism on Domain controller???? 2) When DC1 Goes Down, Then DFS( Distributed File System) can not be Queried /Accessible. 3) Why We Use ADC i.e ADC provides which Network Services ? 4) I want to have the complete automated Fail_Over and Fail_Back mechanism of domain controllers and DFS, so that windows XP and Windows 2000 clients recieves correct data. Also Mention that how much Delays are Possible During Fail_Over and Fail_Back to Occur. 5) DNS On Additional Domain Controller should be PRIMARY or SECONDARY ? Any Tutorial, Lecture or Hands on Lab notes, Vedio will be very helpful to me. Sir, Prompt Response will be highly appretiated. Regards


Does the replication actually keep copied of all shared data or just the share structure?


This article on DFS is a perfect mix of detail and brevity. Thank you for an excellent 'how-to' piece on DFS.


what is does is give a new URL to file shares. It does not copy any data. However it's usefulness is this. Simplify a share URL. In larger and more complex networks, you can have a slew of fileshares all over the place. Using DFS you can keep them where they are and have people map to the new share (DFS share). Also, long URL's can be simplified. Even if the share itself moves to a different location (computer) you can keep them mapped to the data by using the same DFS share. It is nice to map to something like \\Fileshares\finance or \\fileshares\legal rather than \\WhatWasThatComputernameAgain\ShareName_WHA??? You can build the entire share structure around it. However, in my experiences (not on the server side), DFS shares seem to have issues. Often they add hang time to open and often they just dont work right. However it is very possible that the reason is, at my work, they just arent doing it right (or keep playing with routing tables).


Thanks for clarifying, all clear now.

Editor's Picks