From 478e73afeef1f02896a21071ed6c364d568bd215 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Tue, 14 Oct 2025 04:59:34 -0600 Subject: [PATCH] Update Workflows/Windows/Windows Server/Roles/DFS/Creating and Configuring DFS Namespaces with Replication.md --- ...eating and Configuring DFS Namespaces with Replication.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Workflows/Windows/Windows Server/Roles/DFS/Creating and Configuring DFS Namespaces with Replication.md b/Workflows/Windows/Windows Server/Roles/DFS/Creating and Configuring DFS Namespaces with Replication.md index d3dc673..d5cc150 100644 --- a/Workflows/Windows/Windows Server/Roles/DFS/Creating and Configuring DFS Namespaces with Replication.md +++ b/Workflows/Windows/Windows Server/Roles/DFS/Creating and Configuring DFS Namespaces with Replication.md @@ -20,9 +20,9 @@ Install the roles on **both servers**: * **Next → Next → Install**, then finish. ### Create & Configure Network Shares -Create (or identify) the folders you want to publish in the namespace, and share them on **each** server. Be sure to enable **Access-based Enumeration** on all of the folder shares for additional security. +Create (or identify) the folders you want to publish in the namespace, and share them on **each** server. Be sure to enable **Access-based Enumeration** on all of the folder shares for additional security. You only need to ensure that the folders exist on one of the servers, it will be created on-the-fly and replicated automatically. -Additionally, it is recommended (if possible) to set the share names to be hidden. For example `\\LAB-FPS-01\Projects$`, that way it ensures that users access the share via DFS at `\\bunny-lab.io\Projects` and users don't accidentally access the file servers directly, bypassing DFS. For example, the local path would be `Z:\Projects` but the network share would be `\\LAB-FPS-01\Projects$`. *This wouldn't break things like replication, but it would muck things up a little bit organizationally.* +Additionally, it is recommended (if possible) to set the share names to be hidden. For example `\\LAB-FPS-01\Projects$`, that way it ensures that users access the share via DFS at `\\bunny-lab.io\Projects` and users don't accidentally access the network shares directly, bypassing DFS. For example, the local path would be `Z:\Projects` but the network share would be `\\LAB-FPS-01\Projects$`. *This wouldn't break things like replication, but it would muck things up a little bit organizationally.* !!! warning "What must match vs. what can differ" - **Must exist on each server:** a shared folder to act as the *folder target* (path can differ per server). @@ -77,6 +77,7 @@ Create the DFS folders and add folder targets: * **Add** folder targets (one per server), e.g.: * `\\LAB-FPS-01\Projects$\Scripting` * `\\LAB-FPS-02\Projects$\Scripting` + * You may be prompted to create the folder because it does not exist on `LAB-FPS-02`, in this circumstance, you can tell it to create the folder automatically with read-only permissions. *Don't worry, when replication from `LAB-FPS-01` occurs, NTFS permissions will be overwritten to the correct users and groups.* * When prompted *"Create a replication group to synchronize the folder targets?"*, click **Yes** to launch the DFS Replication wizard. !!! info "**Be patient**"