bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Workflows/Windows/Windows Server/Roles/DFS/Setting Up DFS Across Multiple File Servers.md
All checks were successful
GitOps Automatic Deployment / GitOps Automatic Deployment (push) Successful in 8s
Details

Browse Source
This commit is contained in:
Nicole Rappe
2025-10-13 22:03:50 -06:00
parent c2a79839b3
commit d37b504091
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -19,7 +19,10 @@ 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. You will want to ensure the following minimum permissions are configured:
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.
!!! warning "Replicate Folders and Permissions Across all File Servers"
It is important for you to understand that every member server of the DFS namespaces and replication need to be configured identically, with the same local drive letters and folder structures. The data for the shares only needs to exist on one server to ensure it can be replicated across to the other member servers of the DFS namespaces.
| **Permission Type** | **User / Group** | **Access Level** |
| :--- | :--- | :--- |
@@ -33,4 +36,4 @@ The next step in the process is to ensure that the network shares that will be s
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 on both locations.