Update Workflows/Windows/Windows Server/Roles/DFS/Setting Up DFS Across Multiple File Servers.md

Workflows/Windows/Windows Server/Roles/DFS/Setting Up DFS Across Multiple File Servers.md

@@ -33,9 +33,19 @@ The next step in the process is to ensure that the network shares that will be s
 | NTFS | `Share_Admins` | Full Control | This is a security group I created for admins to manage the data on network shares unilaterally. |
 | NTFS | *<Any Users / Groups That Need Access>* | Modify | This is for anyone who needs access to these specific files / folders. |
 
-### DFS Management 
-#### DFS Breakdown
+!!! info "Disable Permission Inheritance"
+    It's just more organized to keep permission inheritance turned-off for the share, so parent folder permissions don't influence it, which could cause unexpected issues in the future if the parent's permissions were changed.
+
+### DFS Breakdown
 At this point, we need to create a DFS "Namespace".  This is basically a logical representation of either a single or a group of individual folders on one or more file servers.  The files and folders appear under a singular location like `\\bunny-lab.io\Projects\Scripting`.  In this example, `Projects` is the namespace (Its not a real folder with data), and `Scripting` is a folder replicated across one or more file servers, mapping to a real (generally hidden) network share like `\\LAB-FPS-01\Projects$\Scripting`.  In this example, there is a network share located at `Projects$` that (organizationally) correlates to the `Projects` DFS namespace, but you should not put files and folders in this root location, as it can cause issues or introduce potential corruption.
 
-#### DFS Configuration
-Now, we need to start working on actually setting up DFS now that the shares exist (and are configured identically) on both locations.
+### DFS Configuration
+Now, we need to start working on actually setting up DFS now that the shares exist (and are configured identically) on all member servers.  You can choose to do these steps on any of the member servers, but I recommend using the lowest number server (e.g. `LAB-FPS-01`).  The configurations will be automatically replicated across to all member servers from the server you choose to configure, so in reality, it really doesn't matter which server you choose.
+
+#### Create Namespace(s)
+- Navigate to "**Server Manager > Tools > DFS Management**"
+- In the left-hand sidebar, right-click "Namespaces" > "**New Namespace...**"
+    - Choose a member server (e.g. `LAB-FPS-01`) then click "**Next**"
+    - Give a name to the namespace (e.g. `Projects`) then click "**Next**"
+        - You do *not* need to click on the "Edit Settings" button.  Just leave all of the settings as-is with `All users have read-only permissions` as this permission controls the namespace configuration data permissions in `C:\DFSRoots\<Namespace>`
+    -