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:
- From the Start menu, select Administrative Tools | Distributed File System to access the Microsoft Management Console shown in Figure A.
- Right-click on the Distributed File System and select New DFS Root to launch the New DFS Root Wizard.
- Click Next and select the type of DFS root you want to create from the screen shown in Figure B.
- Select the Domain and click Next.
- Enter the fully qualified domain name (FQDN) of the host server, as shown in Figure C, and then click Next.
- Select a DFS root share from the screen shown in Figure D and click Next.
- Click Next and then click Finish, and you’ll see something similar to Figure E.
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:
- Right-click on your DFS root and select New DFS Link.
- Enter the name of the DFS link.
- Browse your network to the shared folder, as we’ve done in Figure G, and click OK.
- 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:
- Select Active Directory Users And Computers from the Administrative Tools folder. Right-click on your domain and choose New | Shared Folder.
- Enter the name and network path to the DFS share, as shown in Figure I, and click OK.
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:
- Open DFS from the Administrative Tools folder.
- 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.