Table of Contents
Microsoft - Windows - DFS
Microsoft TechNet - DFS Technical Reference
Microsoft TechNet - How DFS Works
Microsoft TechNet - Distributed File System Replication: Frequently Asked Questions
Microsoft TechNet - DFS Replication scalability guidelines
Microsoft TechNet - Overview of the Distributed File System Solution in Microsoft Windows Server 2003 R2
Monitoring and Troubleshooting the File Replication Service
Windows 2000 Dfs Resources from LabMice.net
Viewing DFS Link Limitations
LasCon Storage - Windows File Systems - DFS
Blogposts/Articles
The Storage Team at Microsoft - File Cabinet Blog:
Troubleshooting erroneous sharing violations in the DFS Replication health report
Understanding DFS Replication "limits"
DFS Replication: What’s new in Windows Server™ 2008
DFSUtil in Windows Server 2003 VS DFSUtil in Windows Server 2008
What does DFSDiag do?
Think Big - with Powershell - DFS link count check
DFS Replication Improvements in Windows Server 2012
DFS Replication in Windows Server 2012 R2: Revenge of the Sync
DFS Replication Initial Sync in Windows Server 2012 R2: Attack of the Clones
Jose Barreto's Blog - Using the Windows Server 2008 DFSUTIL.EXE command line to manage DFS-Namespaces
Ask the Directory Services Team - DFS Override Referral Ordering, Messing with the Natural Order
Ask the Directory Services Team - Common DFSN Configuration Mistakes and Oversights
Microsoft KB Articles
KB2951262 - List of currently available hotfixes for Distributed File System (DFS) technologies in Windows Server 2012 and Windows Server 2012 R2
KB968429 - List of currently available hotfixes for Distributed File System (DFS) technologies in Windows Server 2008 and in Windows Server 2008 R2
KB958802 - List of currently available hotfixes for Distributed File System (DFS) technologies in Windows Server 2003 and in Windows Server 2003 R2
KB819106 - DFS shares appear to be empty when they are accessed by client computers that are running Windows 95, Windows 98, or Windows 98 Second Edition
KB290075 - Distributed File System Links May Not Be Visible When You Connect to the Distributed File System Root Share
KB938112 - When you try to connect to a DSF root shared folder from a client computer that is running Windows XP, the client computer cannot recognize a DFS link
DFS namespace folders are deleted after you restart a Windows Server 2008 R2-based computer (2761922) has a hotfix for the reparse points (the links in the DFS root folder) disappearing on the filesystem of a DFS Namespace server after it is restarted. Workaround is to restart the DFS Namespace service on the affected DFS Namespace server.
Tuning
Troubleshooting
DFS replication: Inter-site problems beschrijft problemen met inter-site full-mesh dfs replicatie. Opgelost door benoemen extra bridgehead servers via AD Sites and Services console.
Domain DFS from a non-domain joined client
Marco Di Feo - DFSN Performance, where are you? on 2014-01-16 with Windows Server 2008 R2.
Poorten voor DFS beperken
collin bowern - Locking Down DFS for Windows Firewall Zie hiervoor:
Microsoft Support - How to configure RPC to use certain ports and how to help secure those ports by using IPsec KB908472
Microsoft Support - How to restrict FRS replication traffic to a specific static port KB319553
Microsoft Support - Service overview and network port requirements for the Windows Server system KB832017
Windows Search Services not supported on DFS Namespace
Still not supported in Windows Server 2012 R2.
Sources:
Spiceworks - Windows server namespaces / DFS vs Windows Search Indexing
Microsoft Forums - WDS 4.0 and DFS
Server Fault - Windows 7 clients can't search indexed files on Server 2008 R2 file server
Ars Technica > Forums > Operating Systems & Software > Windows Technical Mojo > Indexing File Shares (DFS and MSCS, oh joy.)
Troubleshooting
DFS Root Target verwijderen op Server 2003 (als desbetreffende server al ter ziele is)
Als een DFS Root Target server nog beschikbaar is, kun je via de Distributed File System console of dfsutil /RemFtRoot de root target verwijderen uit de DFS namespace.
Echter als de server al ter ziele is, dan zijn beide opties niet te gebruiken.
De oplossing in zo'n geval is om dfsutil met de optie /UnmapFtRoot te gebruiken. Hiervoor hoeft de te verwijderen Root Target server niet meer online te zijn.
Dit kan met het volgende commando:
dfsutil /unmapftroot \\(netbios)domeinnaam\dfssharenaam /server:teverwijderenroottargetserver /share:dfssharenaam
Volgens Help and Support van Windows Server 2003, zou de /share parameter voorzien moeten worden van \\(netbios)domeinnaam\dfssharenaam, maar dat werkt niet. Het opgeven van alleen de sharenaam werkt wel.
Bron:John Howard - How to remove a failed server from DFS in Windows Server 2003 R2
Zie ook:Seven-Winds Blog - How to remove a Domain DFS Name space with a decommissioned server?
Create DFSR Health Report for Server 2012 SYSVOL
dfsradmin health new /RgName:"Domain System Volume" /RefMemName:domain\DC-FQDN /RepName:C:\TEMP\report.html /FsCount:false
Fix Event ID 2213 Source DFSR for SYSVOL on Server 2012
The event:
Log Name: DFS Replication Source: DFSR Date: 10-5-2013 13:50:48 Event ID: 2213 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: DC01.DOMAIN.LOCAL Description: The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication. Additional Information: Volume: C: GUID: <GUID> Recovery Steps 1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders. 2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command: wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="<GUID>" call ResumeReplication For more information, see http://support.microsoft.com/kb/2663685.
The fix:
- Make a backup of C:\Windows\SYSVOL\ on every Domain Controller.
- Execute the following in an elevated command prompt on the DC that generated event id 2213:
wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="<GUID>" call ResumeReplication
Copy and paste from the command with the correct GUID from the event.
Source:
- The Event ID description.