diff --git a/Workflows/Windows/Windows Server/Roles/DFS/Deploying DFS.md b/Workflows/Windows/Windows Server/Roles/DFS/Deploying DFS.md
index b243b72..e66c467 100644
--- a/Workflows/Windows/Windows Server/Roles/DFS/Deploying DFS.md	
+++ b/Workflows/Windows/Windows Server/Roles/DFS/Deploying DFS.md	
@@ -19,4 +19,18 @@ The first step you want to perform is installing the necessary roles on *both se
 - Click the "**Install**" button and wait for the installation to finish.
 
 ### Create & Configure Network Shares
-The next step in the process is to ensure that the network shares that will be shared via DFS have sane permissions.  
\ No newline at end of file
+The next step in the process is to ensure that the network shares that will be shared via DFS have sane permissions.  You will want to ensure the following minimum permissions are configured:
+
+| **Permission Type** | **User / Group** | **Access Level** |
+| :--- | :--- | :--- |
+| Share | `Authenticated Users` | Full Control |
+| NTFS | `SYSTEM` | Full Control |
+| NTFS | `Share_Admins` | Full Control |
+| NTFS | *<Any Users / Groups That Need Access>* | Modify |
+
+### DFS Management 
+#### 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
+