User Tools

Site Tools


microsoft:windows:dfs

Microsoft - Windows - DFS

Blogposts/Articles

Microsoft KB Articles

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

Windows Search Services not supported on DFS Namespace

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:

  1. Make a backup of C:\Windows\SYSVOL\ on every Domain Controller.
  2. 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:

microsoft/windows/dfs.txt · Last modified: 2023/07/26 11:03 by bas

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki