File Management with Distributed File System (DFS) and Replication

Overview

The Distributed File System (DFS) is a Windows Server role service with two components that work together to simplify file access across multiple servers. DFS Namespaces lets you present shared folders from different servers under a single unified UNC path – users connect to \\std.local\share\Common instead of needing to know which physical server hosts which share. DFS Replication automatically keeps the contents of those folders synchronized across servers, so files written on one server appear on all others within minutes.

In this guide, we configure a domain-based DFS namespace on two servers (SRV01 and SRV02), add both as namespace servers, create folder targets backed by D:\Common on each server, configure share permissions, and set up DFS Replication with a replication group named Common_Rep – so any file written through the namespace is automatically replicated to both servers.

Prerequisites

Two Windows Server machines (SRV01 and SRV02) joined to the domain std.local
Domain Admin or Enterprise Admin permissions
A D:\Common folder created locally on both SRV01 and SRV02
Network connectivity between the two servers

Part 1 – Install the DFS Roles

DFS Namespaces and DFS Replication are both role services under File and Storage Services. They must be installed on every server that will participate in the namespace or replication group. Run the Add Roles and Features Wizard on both SRV01 and SRV02.

Step 1 – Select the DFS Role Services

In Server Manager, click Manage and select Add Roles and Features. Work through the wizard until you reach File and Storage Services. Expand File and iSCSI Services and check both DFS Namespaces and DFS Replication.

Server Manager Add Roles and Features wizard with DFS Namespaces and DFS Replication checkboxes selected under File and iSCSI Services — Selecting DFS Namespaces and DFS Replication under File and iSCSI Services – install both on every participating server

Step 2 – Confirm and Install

On the Confirmation page, review the selected features and click Install. The wizard installs both DFS role services and the DFS Management console. Repeat the installation on SRV02 before continuing.

Add Roles and Features wizard Confirmation page listing the selected DFS role services ready for installation — Confirming the role selection – click Install to begin

Add Roles and Features Results page showing installation succeeded for DFS Namespaces and DFS Replication — Installation completed successfully – both DFS role services are now installed on this server

Part 2 – Create a DFS Namespace

A DFS Namespace provides the unified path that users connect to. We will create a domain-based namespace, which stores its configuration in Active Directory and supports multiple namespace servers for high availability. The namespace path will be \\std.local\share.

Step 3 – Open DFS Management

In Server Manager, go to Tools and select DFS Management. The console opens with two root nodes in the left panel: Namespaces (for folder namespace configuration) and Replication (for managing replication groups).

DFS Management console showing the Namespaces and Replication nodes in the left panel tree — The DFS Management console – the central tool for configuring both DFS Namespaces and DFS Replication

Step 4 – Start the New Namespace Wizard

Right-click the Namespaces node and select New Namespace. On the first wizard page, enter the name of the server that will host the namespace root – in this case, SRV01. Click Next.

New Namespace Wizard server selection page with SRV01 entered as the namespace hosting server — Specifying SRV01 as the first namespace server – additional namespace servers can be added after the wizard completes

Step 5 – Enter the Namespace Name and Select Type

Enter share as the namespace name. The wizard shows a preview of the full path: \\std.local\share. On the Namespace Type page, select Domain-based namespace. This stores the namespace configuration in AD DS and makes it available from multiple namespace servers – providing fault tolerance when SRV02 is added as a second server.

New Namespace Wizard showing 'share' entered as the namespace name with the full path preview \\std.local\share, and Domain-based namespace type selected — Naming the namespace ‘share’ and selecting Domain-based – the full UNC path will be \\std.local\share

Step 6 – Complete the Namespace Wizard

Review the namespace settings on the summary page and click Create. The namespace \\std.local\share is created and immediately visible in the DFS Management console under Namespaces.

New Namespace Wizard review settings summary page and the DFS Management console showing the newly created \\std.local\share namespace in the tree — The namespace is created – \\std.local\share now appears under Namespaces in DFS Management

Part 3 – Add a Second Namespace Server

Adding SRV02 as a second namespace server means that if SRV01 is unavailable, clients are automatically redirected to SRV02. Right-click your namespace and select Add Namespace Server, enter SRV02, and click OK. Both servers now appear in the Namespace Servers tab with their referral paths listed.

DFS Management showing the \\std.local\share namespace with both SRV01 and SRV02 listed as namespace servers with their respective referral paths — Both servers are now namespace servers – DFS refers clients to either server when they access \\std.local\share

Part 4 – Create Folder Targets

Folder targets define where DFS actually stores the data behind a namespace path. We will create a namespace folder named Common and back it with shared folders on both servers – so \\std.local\share\Common resolves to either \\SRV01\Common or \\SRV02\Common depending on which server the client is referred to.

Step 7 – Add a New Folder to the Namespace

In DFS Management, right-click your namespace (\\std.local\share) and select New Folder. Enter Common as the folder name – the preview path updates to \\std.local\share\Common. Click Add to begin configuring the folder targets.

New Folder dialog with 'Common' entered as the folder name, showing \\std.local\share\Common as the namespace path preview and the Add button highlighted in the Folder targets section — Creating the Common folder in the namespace – Add opens the folder target configuration

Step 8 – Add Folder Targets for Both Servers

Click Add, then Browse to navigate to SRV01. Select the Common folder under the D drive. The wizard prompts you to create a network share – enter Common as the share name with local path D:\Common. Click OK three times. Then add a second target pointing to SRV02’s Common folder using the same steps.

Browse For Folder dialog showing D:\Common selected on SRV01, and the Create Share dialog with share name 'Common' and local path D:\Common entered — Selecting D:\Common on SRV01 and creating the share – this becomes the first folder target for \\std.local\share\Common

New Folder dialog showing two folder targets - \\SRV01\Common and \\SRV02\Common - both configured, with a Replication prompt asking whether to create a replication group automatically — Both folder targets are configured – click No on the replication prompt to configure DFS Replication manually in Part 6

Part 5 – Configure Share Permissions

By default, the shares created by the wizard grant read-only access to Everyone. Users accessing the namespace will see the Common folder but cannot create or modify files until write permissions are explicitly granted on each share.

Step 9 – Verify Namespace Access and Identify the Permission Issue

Open File Explorer and navigate to \\std.local\share – the Common folder should be visible. Attempting to create a file inside it produces a Destination Folder Access Denied error. To resolve this, open DFS Management, expand your namespace, right-click the \\SRV01\Common entry, and select Properties.

File Explorer showing \\std.local\share with Common folder visible, a Destination Folder Access Denied error dialog, and DFS Management with Properties selected on the SRV01 folder target — The namespace is accessible but files cannot be created – share permissions must be updated on each folder target

Step 10 – Grant Write Permissions on the Shared Folder

In the Properties dialog for \\SRV01\Common, click Share Permissions. In the Permissions dialog, check Full Control, Change, and Read for Everyone, then click OK. Repeat this for the SRV02 folder target. After updating both, file creation through the namespace path succeeds.

\\SRV01\Common Properties dialog showing the Share Permissions button, and the Permissions for Common dialog with Everyone's Full Control, Change, and Read checkboxes all checked — Granting Everyone Full Control, Change, and Read on the share – apply the same permissions to the SRV02 target

Part 6 – Configure DFS Replication

Without replication, files written through the namespace only exist on whichever server processed the write. DFS Replication creates a replication group that automatically synchronizes D:\Common across both servers – so regardless of which server a client is referred to, it always sees the same files.

Diagram showing SRV01 and SRV02 each connected to a Namespace Root with their D:\Common network shares, and a DFS Replication arrow synchronizing the two servers - alongside DFS Management with New Replication Group selected from the Replication context menu — DFS Replication keeps D:\Common identical on both servers – without it, files written to SRV01 are not visible from SRV02

Step 11 – Select Replication Group Type and Name

In DFS Management, right-click Replication and select New Replication Group. On the Group Type page, select Multipurpose replication group – this supports bidirectional replication between two or more servers. On the Name and Domain page, enter Common_Rep as the replication group name and confirm the domain is std.local. Click Next.

New Replication Group Wizard showing Multipurpose replication group selected on the Group Type page, and Common_Rep entered on the Name and Domain page with std.local as the domain — Multipurpose replication group named Common_Rep – this will synchronize D:\Common bidirectionally between SRV01 and SRV02

Step 12 – Add Replication Group Members

On the Replication Group Members page, click Add. In the Select Computers dialog, type SRV01; SRV02, click Check Names, then OK. Both servers appear in the members list with their domain. Click Next.

Select Computers dialog with SRV01; SRV02 entered in the object names field, and the Replication Group Members page showing both SRV01 and SRV02 added in the std.local domain — Adding SRV01 and SRV02 as members of the Common_Rep replication group

Step 13 – Configure Topology and Bandwidth

Select Full mesh for the topology – this connects every member directly to every other member, which is the correct choice for a two-server setup. For the replication schedule, select Replicate continuously using the specified bandwidth and set bandwidth to Full. Since both servers are on the same LAN, continuous full-bandwidth replication provides near-instant file synchronization.

Topology Selection page with Full mesh selected, and the Replication Group Schedule and Bandwidth page with continuous replication and Full bandwidth chosen — Full mesh topology with continuous full-bandwidth replication – the right setting for servers on the same local network

Step 14 – Select Primary Member and Specify Folders to Replicate

On the Primary Member page, select SRV01. The primary member is the authoritative data source for the initial replication cycle – its files will be copied to all other members first. On the Folders to Replicate page, click Add, then Browse to navigate to D:\Common on SRV01.

Primary Member page with SRV01 selected in the dropdown, and the Folders to Replicate page with an empty list and the Add button highlighted — SRV01 is designated as primary – its D:\Common content will be the authoritative starting point for initial replication

Add Folder to Replicate dialog showing Browse For Folder with D:\Common selected on SRV01, and the replicated folder name automatically set to Common — Selecting D:\Common on SRV01 as the folder to replicate – the wizard derives the replicated folder name ‘Common’ from the path

Step 15 – Configure the Replicated Folder Path on Other Members

After adding the primary folder, the wizard shows the Local Path of Common on Other Members page. SRV02 is listed as <Not Set> / Disabled. Click Edit, set membership status to Enabled, and browse to select D:\Common on SRV02.

Folders to Replicate page showing D:\Common listed with replicated folder name Common, then the Local Path of Common on Other Members page with SRV02 showing Not Set and Disabled status, with Edit highlighted — The wizard requires a local path on each non-primary member – click Edit to configure SRV02’s replicated folder location

Edit dialog for SRV02 with Enabled membership status selected and Browse For Folder open showing D:\Common selected under SRV02.std.local — Setting SRV02’s membership status to Enabled and selecting D:\Common as the local path for the replicated folder

Step 16 – Review Settings and Create the Replication Group

Once SRV02 shows D:\Common and Enabled in the members list, click Next. Review the summary of all replication group settings, then click Create. The wizard runs through all configuration tasks – when the Confirmation page shows every item as Success, click Close.

Local Path of Common on Other Members showing SRV02 with D:\Common and Enabled status, the Review Settings and Create Replication Group summary page, and the Confirmation page with all tasks showing Success — All configuration steps report Success – the Common_Rep replication group is now active and will begin initial synchronization

Step 17 – Verify the Replication Group in DFS Management

The Common_Rep replication group now appears under the Replication node in DFS Management. Initial synchronization time depends on network speed and data volume. For a new, mostly empty share this happens within seconds; for large data sets it may take longer.

DFS Management console showing the Common_Rep replication group listed under the Replication node with SRV01 and SRV02 visible as members — Common_Rep is active in DFS Management – the Memberships tab shows the status of replication on each member server

Step 18 – Confirm Replication is Working

After a few minutes, open File Explorer and navigate to both \\SRV01\Common and \\SRV02\Common in separate windows. Both folders should now contain the same files. In this example, four text documents created on SRV01 are now visible on SRV02 as well – confirming that DFS Replication is synchronizing the folders correctly.

Two File Explorer windows side by side showing \\srv01\Common and \\srv02\Common each containing the same four New Text Documents, confirming successful DFS Replication — Both servers contain the same files – DFS Replication is working and D:\Common is synchronized across SRV01 and SRV02

Important Considerations

Staging Folder Size

DFS Replication uses a staging folder on each member to hold replicated files in transit. The default staging quota is 4 GB. In environments with large files – such as virtual machine images, database backups, or large media files – this default can cause replication to stall. Increase the staging quota in the replication group member properties under the Staging tab.

Replication Latency

Replication is near-instant on a LAN with continuous full-bandwidth replication enabled, but it is not synchronous. There is always a brief window between when a file is written and when it appears on other members. Over WAN links, use scheduled replication with bandwidth throttling to avoid saturating slower connections, and set expectations accordingly for file availability across sites.

Namespace Type and Active Directory

Domain-based namespaces require a functioning Active Directory domain controller to resolve. If the DC is unreachable, clients may be unable to navigate the namespace even if the file servers themselves are online. For environments where AD availability is a concern, consider configuring standalone namespaces or ensuring multiple DCs are accessible from all sites.

Conflict Resolution

If the same file is modified on two different servers simultaneously – before replication has synced the changes – DFS Replication applies a last writer wins policy. The most recently modified version is replicated to all members, and the losing version is moved to the hidden DfsrPrivate\ConflictAndDeleted folder on the affected member. In environments with high concurrent write activity from multiple locations, monitor this folder periodically to catch any conflicts.

Tags: #Active Directory #DFS #File Server #Namespace #Replication #Windows Server