Update services/file-services/windows-server/DFS Namespaces with Replication.md
This commit is contained in:
@@ -129,7 +129,8 @@ In the Replication wizard that appears after about a minute, you can configure t
|
|||||||
- ✅Update folder properties
|
- ✅Update folder properties
|
||||||
- ✅Create connections
|
- ✅Create connections
|
||||||
|
|
||||||
### Checking DFS Status
|
### Troubleshooting / Diagnostics
|
||||||
|
#### Checking DFS Status
|
||||||
You may want to put together a simple table report of the DFS namespaces, replication info, and target folders. You can run the following powershell script to generate a nice table-based report of the current structure of the DFS namespaces in your domain.
|
You may want to put together a simple table report of the DFS namespaces, replication info, and target folders. You can run the following powershell script to generate a nice table-based report of the current structure of the DFS namespaces in your domain.
|
||||||
|
|
||||||
??? example "Powershell Reporting Script"
|
??? example "Powershell Reporting Script"
|
||||||
@@ -394,4 +395,29 @@ You may want to put together a simple table report of the DFS namespaces, replic
|
|||||||
}
|
}
|
||||||
|
|
||||||
Write-DfsGrid -Data $rows
|
Write-DfsGrid -Data $rows
|
||||||
```
|
```
|
||||||
|
|
||||||
|
#### Fixing Inconsistent DFS Management GUI
|
||||||
|
Sometimes the GUI for managing DFS becomes "inconsistent" whereas the namespaces and replication groups are different between member servers, and may be missing namspaces or missing replication groups. DFS Management is an MMC snap-in. MMC persists per-user console state under `%APPDATA%\Microsoft\MMC\`. If that state gets out of sync (common after service hiccups or server crashes), the snap-in can render partial/incorrect namespace/replication trees even when DFS itself is fine. Deleting the cached dfsmgmt* console forces a fresh enumeration. We will also include a few extra commands for extra thouroughness.
|
||||||
|
|
||||||
|
Before anything, we want to make sure that active directory itself is not having replication issues, as this would be a deeper, more complicated issue.
|
||||||
|
```powershell
|
||||||
|
repadmin /syncall /AdeP
|
||||||
|
repadmin /replsummary
|
||||||
|
```
|
||||||
|
|
||||||
|
If AD-level replication is successful and timely, you can proceed to run the commands below (one-line-at-a-time):
|
||||||
|
```sh
|
||||||
|
# Pull-Down DFS Configuration from Active Directory & Restart DFS
|
||||||
|
dfsrdiag pollad
|
||||||
|
net stop dfsr
|
||||||
|
net start dfsr
|
||||||
|
|
||||||
|
# Clear DFS Management Snap-In Cache
|
||||||
|
taskkill /im mmc.exe /f
|
||||||
|
del "%appdata%\Microsoft\MMC\dfsmgmt*"
|
||||||
|
dfsmgmt.msc
|
||||||
|
```
|
||||||
|
|
||||||
|
!!! success "DFS Management GUI Restored"
|
||||||
|
At this point, the DFS Management snap-in (should) be successfully showing all of the DFS namespaces and replication groups.
|
||||||
Reference in New Issue
Block a user