Study guide
13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R)
Administering Windows Server Hybrid Core Infrastructure AZ-800
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About Exam AZ-800: Format, Scoring & the September 2026 Retirement
2 Chapter 1: Active Directory Domain Services Architecture & Deployment
1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships
3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join
2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale
4 Chapter 3: Hybrid Identity & Microsoft Entra Integration
3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture
5 Chapter 4: Group Policy in AD DS and Hybrid Environments
4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies
6 Chapter 5: Remote Server Management in Hybrid Environments
5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion
7 Chapter 6: Hybrid Management with Azure Arc and Azure Services
6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers
8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration
7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization
9 Chapter 8: Hyper-V High Availability, Security & Containers
8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry
10 Chapter 9: Azure IaaS Virtual Machine Administration
9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity
11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution
10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC
12 Chapter 11: IP Addressing, DHCP & IPAM Management
11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments
13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access
12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections
14 Chapter 13: File Services, DFS, SMB & Azure File Sync
13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync
15 Chapter 14: Windows Server Storage Infrastructure & High Availability
14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O
13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R)
Key Takeaways Explain This Topic AI
A domain-based namespace stores its configuration in Active Directory and supports multiple namespace servers; a standalone namespace stores it in the local registry and needs a failover cluster for high availability.
Referral ordering is site-cost aware by default, so clients are directed to the folder target in the lowest-cost site before any other target.
The DFS-R staging folder must be at least as large as the 32 largest files in the replicated folder, or replication stalls with staging-quota events.
DFS-R resolves simultaneous edits with last-writer-wins and moves the losing copy to the hidden ConflictAndDeleted folder rather than merging.
DFS-R cannot replicate open files, which is why it is unsuitable as a disaster-recovery engine for databases or running virtual machines.
Last updated: August 2026
DFS Namespaces (DFS-N) & DFS Replication (DFS-R)
Enterprise distributed storage requires presenting geographically dispersed file shares under a unified, fault-tolerant path. Windows Server accomplishes this through two complementary technologies in the Distributed File System (DFS) suite: DFS Namespaces (DFS-N) virtualises the path so that users never learn a server name, and DFS Replication (DFS-R) keeps the folder targets behind that path consistent with each other.
Mastering namespace types, site-cost referral algorithms, multi-master replication topology design, staging folder sizing formulas and conflict resolution behaviour is essential for AZ-800 certification — and DFS-R in particular reappears later in this chapter as the technology that Azure File Sync replaces.
1. DFS Namespaces (DFS-N) Architecture
DFS Namespaces (DFS-N) provides a virtualized view of shared folders across multiple servers. Instead of mapping drive letters to physical server UNC paths (e.g., \\Server01\Finance ), users access a single logical namespace path (e.g., \\contoso.com\Public\Finance ). +-----------------------------------------------------------------------------------+
- | DFS NAMESPACE (DFS-N) TOPOLOGY |
- | |
- | [Unified Namespace UNC] ---> \\contoso.com\CorpData |
- | | |
- | +---------------------------+---------------------------+ |
- | | | |
- | v v |
- | [Folder: \Docs] [Folder: \Software] |
- | Folder Targets: Folder Targets: |
- | - \\NY-FS01\Docs (Active Site: NewYork) - \\LON-FS01\Soft |
- | - \\LON-FS01\Docs (Replica Site: London) - \\AZ-FS01\Soft |
- +-----------------------------------------------------------------------------------+
- Standalone vs. Domain-Based Namespaces
- Architectural Attribute Standalone Namespace Domain-Based Namespace (Server 2008 Mode)
- Path Syntax \\ServerName\NamespaceName \\DomainName\NamespaceName (or \\FQDN\Namespace )
Metadata Storage Stored locally in the server's Windows Registry Stored in Active Directory Domain Services (AD DS)
High Availability Requires Windows Server Failover Clustering (WSFC) Native Multi-Master HA via multiple Namespace Servers
- Scalability Up to 50,000 folders with targets > 50,000 folders with targets (2008 Mode)
- Access-Based Enumeration Supported Fully Supported (Hides unauthorized DFS links)
- Search Integration Supported Supported
Important
Windows Server 2008 Mode Requirements: Domain-based namespaces should always be created in Windows Server 2008 Mode . This mode requires a domain functional level of Windows Server 2008 or higher and stores namespace metadata in Active Directory using an optimized directory format that supports Access-Based Enumeration and scales beyond 50,000 folders.
Namespace Referral Ordering Mechanics
When a client queries a DFS namespace folder, the Namespace Server returns a referral list containing the available folder targets ordered by Active Directory Site topology:
Lowest Cost: Targets located in the client's local Active Directory site are placed at the top of the referral list in random order. If no local targets exist, targets in sites with the lowest site link cost are listed next.
Random Order: Targets are sorted randomly, ignoring site boundaries (useful for simple load balancing across identical network links).
Exclude Targets Outside the Client's Site: Prevents the client from failing over to remote branch or cloud targets across expensive WAN links if local targets become unavailable. # Install DFS Namespaces role service
Install-WindowsFeature -Name FS-DFS-Namespace -IncludeManagementTools
- # Create a new Domain-Based DFS Namespace in Windows Server 2008 Mode
- New-DfsnRoot `
- TargetPath '\\NY-FS01\CorpRoot' `
- Type DomainV2 `
- Path '\\contoso.com\CorpData' `
- Description 'Central Enterprise Namespace'
- # Add a second Namespace Server for high availability
- New-DfsnRootTarget `
- TargetPath '\\LON-FS01\CorpRoot' `
- Path '\\contoso.com\CorpData'
# Add a folder with targets and configure Referral Ordering
New-DfsnFolder -Path '\\contoso.com\CorpData\Finance' -TargetPath '\\NY-FS01\Finance' -EnableTargetFailback $true
Set-DfsnFolderTarget -Path '\\contoso.com\CorpData\Finance' -TargetPath '\\NY-FS01\Finance' -ReferralPriorityClass SiteCostNormal
2. DFS Replication (DFS-R) Architecture
DFS Replication (DFS-R) is a state-based multi-master replication engine designed to synchronize folder contents across servers over constrained WAN connections. +-----------------------------------------------------------------------------------+
- | DFS REPLICATION (DFS-R) TOPOLOGY |
- | |
- | [HUB-AND-SPOKE TOPOLOGY] [FULL MESH TOPOLOGY] |
- | |
- | [Central Hub] [Node A] <-----> [Node B] |
- | / | \ ^ ^ |
- | v v v | \ / | |
- | [Spoke 1] [Spoke 2] [Spoke 3] | \ / | |
- | (Branch 1) (Branch 2) (Branch 3) v X v |
- | * Spoke-to-Spoke traffic blocked [Node C] <-----> [Node D] |
- | * Scalable for > 10 branch offices * <= 10 servers only |
- +-----------------------------------------------------------------------------------+
- Topology Comparison
Full Mesh: Every replication member communicates directly with every other member. Highly redundant, but replication connections scale quadratically: N × ( N − 1 ) / 2 N \times (N - 1) / 2 N × ( N − 1 ) /2 . Suitable only for small clusters ( ≤ 10 \le 10 ≤ 10 servers).
Hub-and-Spoke: Central hub servers replicate to multiple branch spoke servers. Spokes replicate exclusively with hubs, eliminating branch-to-branch WAN traffic. Highly scalable for large branch office networks.
3. DFS-R Staging Folder Sizing & RDC Optimization
DFS-R processes inbound and outbound file changes through dedicated Staging Folders located under the hidden System Volume Information\DFSR\Staging directory. +-----------------------------------------------------------------------------------+
- | DFS-R STAGING & RDC COMPRESSION PIPELINE |
- | |
- | [Source File Modified] |
- | | |
- | v |
- | [Staging Folder] ---> Compresses file & computes RDC sub-file chunk hashes |
- | | |
- | v |
- | [RDC Delta Sync] ---> Transmits ONLY altered binary blocks across WAN |
- | | |
- | v |
- | [Target Staging] ---> Reconstructs full file from local chunks + deltas |
- | | |
- | v |
- | [Target Live Share] ---> Commits updated file to destination folder |
- +-----------------------------------------------------------------------------------+
- Sizing the Staging Folder: The 32 Largest Files Rule
If a staging folder is undersized, DFS-R will repeatedly clean up staged files before replication completes, causing replication thrashing, high disk I/O, event ID 4202/4204 warnings, and severe synchronization delays.
Important
Official Sizing Formula: The staging folder quota on each replication member must be configured to be at least as large as the sum of the 32 largest files in the replicated folder: Staging Folder Quota ≥ ∑ i = 1 32 Size of File i \text{Staging Folder Quota} \ge \sum_{i=1}^{32} \text{Size of File}_i Staging Folder Quota ≥ ∑ i = 1 32 Size of File i For example, if a folder contains large CAD models where the 32 largest files average 500 MB each, the minimum staging quota is 32 × 500 MB = 16 GB 32 \times 500\text{ MB} = 16\text{ GB} 32 × 500 MB = 16 GB (Default is 4,096 MB).
Remote Differential Compression (RDC)
RDC Chunking: When a multi-gigabyte file is modified, RDC calculates cryptographic signatures for small data chunks across the file. Only the changed chunks are transmitted over the network.
Cross-File RDC: DFS-R can locate matching data blocks in different existing files on the destination server, reducing network utilization even when entirely new files are created from existing templates.
4. Conflict Resolution & The ConflictAndDeleted Folder
Because DFS-R is a multi-master replication engine without distributed file locking, simultaneous modifications on different servers trigger conflict resolution.
Conflict Resolution Mechanism: Last-Writer-Wins (LWW)
Timestamp Check: The version of the file with the most recent last-modified timestamp wins.
Tie-Breaker: If timestamps are identical, the file with the highest internal Server GUID / Version Vector wins.
Preserving the Losing Version: The losing file is moved to the hidden ConflictAndDeleted folder located at <ReplicatedFolderPath>\DfsrPrivate\ConflictAndDeleted .
Conflict Manifest: The file is renamed to <OriginalFileName>-[Date]-[GUID] and logged in ConflictAndDeletedManifest.xml . # Check DFS-R backlog between two replication members
Get-DfsrBacklog -SourceComputerName 'NY-FS01' -DestinationComputerName 'LON-FS01' -GroupName 'CorpGroup' -FolderName 'Finance'
# Configure Staging Quota to 32 GB
Set-DfsrMembership -GroupName 'CorpGroup' -FolderName 'Finance' -ComputerName 'NY-FS01' -StagingPathQuotaInMB 32768