Update Workflows/Windows/Windows Server/Roles/DFS/Creating and Configuring DFS Namespaces with Replication.md
All checks were successful
GitOps Automatic Deployment / GitOps Automatic Deployment (push) Successful in 8s
All checks were successful
GitOps Automatic Deployment / GitOps Automatic Deployment (push) Successful in 8s
This commit is contained in:
@@ -95,6 +95,9 @@ Create the DFS folders and add folder targets:
|
||||
#### Configure Replication Group
|
||||
In the Replication wizard that appears after about a minute, you can configure the replication group for the folder:
|
||||
|
||||
!!! info "If Wizard did Not Appear (or Crashed)"
|
||||
In my homelab testing, I had two times when the wizard crashed or simply never opened. If this happens to you, you can manually re-trigger the wizard for the target folder by right-clicking the folder (e.g. `\\bunny-lab.io\Projects\Scripting`) and selecting **Replicate Folder**.
|
||||
|
||||
* **Replication Group Name**: *(leave as suggested)*
|
||||
* **Replicated Folder Name**: *(leave as suggested)*
|
||||
* **Next → Next**
|
||||
@@ -122,15 +125,9 @@ In the Replication wizard that appears after about a minute, you can configure t
|
||||
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.
|
||||
|
||||
```powershell
|
||||
<# Show-DfsTopologyTable.ps1 (PowerShell 5.1 compatible)
|
||||
Table:
|
||||
Namespace | Member Folder Target(s) | Replication Locations | Namespace Servers
|
||||
- One row per folder target (multi-line friendly).
|
||||
#>
|
||||
|
||||
[CmdletBinding()]
|
||||
param(
|
||||
[string]$DomainPrefix = "\\bunny-lab.io" # adjust if needed
|
||||
[string]$DomainPrefix = "\\bunny-lab.io" # Adjust if Different
|
||||
)
|
||||
|
||||
Import-Module DFSN -ErrorAction Stop
|
||||
|
||||
Reference in New Issue
Block a user