How to Configure DFS-R Folder Replication on Windows Server 2025

Start by installing the DFS Replication feature on every server that will participate in folder replication. This includes both the primary and secondary servers.

Open PowerShell as Administrator and run the following command on each server:

Install-WindowsFeature -Name FS-DFS-Replication, RSAT-DFS-Mgmt-Con -IncludeManagementTools

This command installs both the DFS Replication service and the management tools. The installation typically takes 2-3 minutes per server.

Verify the installation by checking the installed features:

Get-WindowsFeature -Name FS-DFS-Replication

The output should show Install State: Installed. Restart the servers if prompted, though it's typically not required for DFS-R installation.

Create identical folder structures on all participating servers. The folders must have matching paths and permissions for DFS-R to work correctly.

On each server, create the folder structure. For this example, we'll use D:\ReplicatedData:

New-Item -Path "D:\ReplicatedData" -ItemType Directory -Force

Create the SMB share with appropriate permissions:

New-SmbShare -Name "ReplicatedData" -Path "D:\ReplicatedData" -FullAccess "Domain Admins" -ReadAccess "Domain Users"

Set NTFS permissions to match the share permissions:

$acl = Get-Acl "D:\ReplicatedData"
$accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule("Domain Users","ReadAndExecute","ContainerInherit,ObjectInherit","None","Allow")
$acl.SetAccessRule($accessRule)
Set-Acl "D:\ReplicatedData" $acl

Verify the share creation:

Get-SmbShare -Name "ReplicatedData"

Test access from another server to ensure network connectivity and permissions are working correctly.

Now create the DFS Replication Group that will manage the folder synchronization. We'll start with a unidirectional setup (hub-and-spoke model).

Open DFS Management from Server Manager: Tools > DFS Management. Alternatively, launch it directly:

dfsmgmt.msc

In the DFS Management console:

1. Right-click Replication in the left pane
2. Select New Replication Group
3. Choose Replication group for data collection for unidirectional replication
4. Enter a descriptive name like "DataReplication-Primary"
5. Add a description: "Primary data replication from SERVER01 to branch servers"

For PowerShell automation, create the replication group with this command:

New-DfsReplicationGroup -GroupName "DataReplication-Primary" -DomainName "yourdomain.com" -Description "Primary data replication group"

Verify the replication group creation:

Get-DfsReplicationGroup -GroupName "DataReplication-Primary"

The command should return the group details including the domain name and description you specified.

Add servers to the replication group and designate the primary member (source) and secondary members (destinations).

In the DFS Management wizard, continue with member configuration:

1. Select the primary member (source server, e.g., SERVER01)
2. Browse and select the folder to replicate: D:\ReplicatedData
3. Click Add to include secondary members (destination servers)
4. For each secondary member, specify the local path: D:\ReplicatedData

Using PowerShell, add members to the replication group:

# Add primary member
Add-DfsrMember -GroupName "DataReplication-Primary" -ComputerName "SERVER01"

# Add secondary members
Add-DfsrMember -GroupName "DataReplication-Primary" -ComputerName "SERVER02", "SERVER03"

Configure the replicated folder and set the primary member:

# Set primary member with read/write access
Set-DfsrMembership -GroupName "DataReplication-Primary" -FolderName "ReplicatedData" -ContentPath "D:\ReplicatedData" -ComputerName "SERVER01" -PrimaryMember $true

# Set secondary members with read-only replication
Set-DfsrMembership -GroupName "DataReplication-Primary" -FolderName "ReplicatedData" -ContentPath "D:\ReplicatedData" -ComputerName "SERVER02"
Set-DfsrMembership -GroupName "DataReplication-Primary" -FolderName "ReplicatedData" -ContentPath "D:\ReplicatedData" -ComputerName "SERVER03"

Verify member configuration:

Get-DfsrMembership -GroupName "DataReplication-Primary"

Check that the primary member shows PrimaryMember: True and secondary members show PrimaryMember: False.

Set up the replication schedule and bandwidth throttling to control when and how fast data replicates between servers.

In the DFS Management wizard, configure the schedule:

1. Choose Replicate continuously using specified bandwidth for real-time sync
2. Set bandwidth limit (e.g., 1024 KB/s) or select Full bandwidth for LAN environments
3. Alternatively, choose Replicate during specified days and times for scheduled replication

For PowerShell configuration, set up a custom schedule:

# Create a schedule for business hours only (8 AM to 6 PM, Monday-Friday)
$schedule = New-Object System.Collections.Hashtable
$schedule.Add("Monday", "08:00-18:00")
$schedule.Add("Tuesday", "08:00-18:00")
$schedule.Add("Wednesday", "08:00-18:00")
$schedule.Add("Thursday", "08:00-18:00")
$schedule.Add("Friday", "08:00-18:00")

# Apply bandwidth throttling (512 KB/s)
Set-DfsrConnectionSchedule -GroupName "DataReplication-Primary" -SourceComputerName "SERVER01" -DestinationComputerName "SERVER02" -ScheduleType UseSchedule -BandwidthDetail @{"08:00-18:00" = 512}

For continuous replication with full bandwidth (recommended for LAN environments):

Set-DfsrConnection -GroupName "DataReplication-Primary" -SourceComputerName "SERVER01" -DestinationComputerName "SERVER02" -DisableConnection $false

Verify the schedule configuration:

Get-DfsrConnection -GroupName "DataReplication-Primary"

The output should show the connection state and any bandwidth limitations you've configured.

Optimize replication performance by configuring staging quotas and Remote Differential Compression (RDC) settings.

Set staging quota (temporary storage for files being replicated). The default is 4% of the replicated folder size, but you may need to increase this for large files:

# Set staging quota to 10 GB (10240 MB)
Set-DfsrMembership -GroupName "DataReplication-Primary" -FolderName "ReplicatedData" -ComputerName "SERVER01" -StagingPathQuotaInMB 10240
Set-DfsrMembership -GroupName "DataReplication-Primary" -FolderName "ReplicatedData" -ComputerName "SERVER02" -StagingPathQuotaInMB 10240

Enable Remote Differential Compression for efficient bandwidth usage:

# Install RDC feature if not already installed
Install-WindowsFeature -Name RDC

# Enable RDC for the replication group
Set-DfsrMembership -GroupName "DataReplication-Primary" -FolderName "ReplicatedData" -ComputerName "SERVER01" -EnableRdc $true
Set-DfsrMembership -GroupName "DataReplication-Primary" -FolderName "ReplicatedData" -ComputerName "SERVER02" -EnableRdc $true

Configure conflict and deleted file retention:

# Set conflict folder quota to 2 GB and retention to 30 days
Set-DfsrMembership -GroupName "DataReplication-Primary" -FolderName "ReplicatedData" -ComputerName "SERVER01" -ConflictAndDeletedQuotaInMB 2048
Set-DfsrMembership -GroupName "DataReplication-Primary" -FolderName "ReplicatedData" -ComputerName "SERVER02" -ConflictAndDeletedQuotaInMB 2048

Verify the configuration:

Get-DfsrMembership -GroupName "DataReplication-Primary" | Select-Object ComputerName, StagingPathQuotaInMB, ConflictAndDeletedQuotaInMB

Check that RDC is enabled:

Get-WindowsFeature -Name RDC

Complete the replication group setup and initiate the first synchronization between servers.

In the DFS Management wizard, review all settings and click Create to finalize the replication group. The wizard will:

1. Create the replication group
2. Add all specified members
3. Configure the replicated folders
4. Start initial synchronization

For PowerShell, force an immediate synchronization:

# Start replication service on all members
Restart-Service -Name DFSR -ComputerName "SERVER01", "SERVER02", "SERVER03"

# Force immediate synchronization
Sync-DfsReplicationGroup -GroupName "DataReplication-Primary" -SourceComputerName "SERVER01" -DestinationComputerName "SERVER02"

Monitor the initial sync progress. Create a test file on the primary server:

# Create test files on primary server
New-Item -Path "D:\ReplicatedData\test-file-$(Get-Date -Format 'yyyyMMdd-HHmmss').txt" -ItemType File -Value "DFS-R Test File Created: $(Get-Date)"

Check replication status:

# Check for any backlog
Get-DfsrBacklog -SourceComputerName "SERVER01" -DestinationComputerName "SERVER02" -FolderName "ReplicatedData" -Verbose

Monitor Event Viewer for DFS Replication events:

Get-WinEvent -LogName "DFS Replication" -MaxEvents 10 | Format-Table TimeCreated, Id, LevelDisplayName, Message -Wrap

A successful initial sync will show Event ID 4104 (Initial sync completed) in the DFS Replication log.

Set up multidirectional (full mesh) replication where all servers can modify files and changes replicate to all other members.

Create a new replication group for multidirectional setup:

# Create multidirectional replication group
New-DfsReplicationGroup -GroupName "Multi-DataReplication" -DomainName "yourdomain.com" -Description "Multidirectional data replication"

# Add all members
Add-DfsrMember -GroupName "Multi-DataReplication" -ComputerName "SERVER01", "SERVER02", "SERVER03"

Configure each member with read/write access (no primary member designation):

# Configure first member
Set-DfsrMembership -GroupName "Multi-DataReplication" -FolderName "SharedData" -ContentPath "D:\SharedData" -ComputerName "SERVER01" -ReadOnly $false

# Configure second member
Set-DfsrMembership -GroupName "Multi-DataReplication" -FolderName "SharedData" -ContentPath "D:\SharedData" -ComputerName "SERVER02" -ReadOnly $false

# Configure third member
Set-DfsrMembership -GroupName "Multi-DataReplication" -FolderName "SharedData" -ContentPath "D:\SharedData" -ComputerName "SERVER03" -ReadOnly $false

Create full mesh connections between all members:

# Create connections between all server pairs
Add-DfsrConnection -GroupName "Multi-DataReplication" -SourceComputerName "SERVER01" -DestinationComputerName "SERVER02"
Add-DfsrConnection -GroupName "Multi-DataReplication" -SourceComputerName "SERVER01" -DestinationComputerName "SERVER03"
Add-DfsrConnection -GroupName "Multi-DataReplication" -SourceComputerName "SERVER02" -DestinationComputerName "SERVER03"

Verify the multidirectional configuration:

Get-DfsrMembership -GroupName "Multi-DataReplication" | Select-Object ComputerName, ReadOnly, PrimaryMember

All members should show ReadOnly: False and PrimaryMember: False for true multidirectional replication.

Perform comprehensive testing to ensure DFS-R is working correctly and troubleshoot any issues.

Test file creation and replication:

# Create test files on primary server
$testFile = "D:\ReplicatedData\replication-test-$(Get-Date -Format 'yyyyMMdd-HHmmss').txt"
Set-Content -Path $testFile -Value "Test file created on SERVER01 at $(Get-Date)"

# Wait 30 seconds then check if file appears on secondary servers
Start-Sleep -Seconds 30
Invoke-Command -ComputerName "SERVER02" -ScriptBlock { Get-ChildItem "D:\ReplicatedData\replication-test*.txt" | Select-Object Name, LastWriteTime }

Check replication health and backlog:

# Check replication health
Get-DfsrState -ComputerName "SERVER01", "SERVER02" | Format-Table ComputerName, State, LastError

# Check for any pending files in backlog
Get-DfsrBacklog -SourceComputerName "SERVER01" -DestinationComputerName "SERVER02" -FolderName "ReplicatedData"

Monitor replication performance:

# Get replication statistics
Get-DfsrFileHash -Path "D:\ReplicatedData" -ComputerName "SERVER01", "SERVER02" | Compare-Object -Property Hash -IncludeEqual

Test conflict resolution (for multidirectional setups):

# Create same filename on two servers simultaneously
Invoke-Command -ComputerName "SERVER01" -ScriptBlock { Set-Content "D:\SharedData\conflict-test.txt" "Content from SERVER01" }
Invoke-Command -ComputerName "SERVER02" -ScriptBlock { Set-Content "D:\SharedData\conflict-test.txt" "Content from SERVER02" }

# Check conflict resolution after 60 seconds
Start-Sleep -Seconds 60
Get-ChildItem "D:\SharedData\*conflict*" -Recurse

Verify Event Logs for successful replication:

# Check for successful replication events
Get-WinEvent -FilterHashtable @{LogName='DFS Replication'; ID=4104,4614} -MaxEvents 5 | Format-Table TimeCreated, Id, Message

Event ID 4104 indicates successful initial synchronization, while 4614 shows successful file replication. Any error events (Warning or Error level) should be investigated immediately.