Skip to main content

Use DFS to Seamlessly Move Redirected Folders and Home Paths to a New Server – Part II

Yesterday we set of DFS on both Windows Server 2003 R2 and Windows Server 2012 R2.  Today we are going through the steps to set up our DFS Namespace and Replication so we can start the transfer of data. 

Add the DFS Namespace

On S1 (Windows Server 2013 R2), click Start à Administrator Tools à DFS Monument

Right click Namespaces and then select New Namespace.

In the Namespace Server window, type S1 and click Next

If you receive this message about the Distributed File System Service is not running, click Yes

image

In the Namespace Name and Settings window, provide the name for the namespace.  In this example, we will use UserData.

Click Edit Settings and select Administrators have full access; other users have read and write permissions

image

Click OK

Click Next

In the Namespace Type window, select Domain-based Namespace and click Next.

Click Create.

Click Close

 

Add the folder targets for both the home and the Redirected folders

Expand Namespaces and right click \\domain\UserInfo

Click New Folder

Provide the name UserHome

image

Click Add

Provide the UNC path to the shared folder for the user’s home profiles.

Click OK twice

Repeat for the redirected documents.

image

Create a replication group between S1 and S2

Go to server S2

In Server Manager click Tools à DFS Management

Right click Replication and select New Replication Group

In the Replication Group Type window, select Multipurpose Replication and click Next.

In the Name and Domain window:

                Name: UserInfoRepGroup

Click Next

In the Replication Group Members window, click Add and add in both servers.

image

Click Next

In the Topology Selection window, select Full Mesh and click Next.

Click Next in the Replication Group Schedule and Bandwidth window.

In the Primary Member window, select S1 from the drop down box and click Next.

In Folders to Replicate click Add.

(You will do this twice. Add both the home profiles and the redirected folders)

image

image

image

Click Next

On the Local Path of Home on Other Members window, you need to add a new local path for both folders on S2.

Click Edit.

Select Enable.

In the local path, enter a valid path.

image

Click OK.

You will receive this message if the path does not exists. Click Yes

image

Click Next

Repeat the process for Documents

image

Click Next

Click Create

Click Close

At this point, you must wait for a full replication. Depending on the amount of data to replicate, this can take a considerable amount of time. Be patient and do not proceed until replication completes.

This is what our configuration looks like now.

image

Tomorrow we will finish this process. We will modify our GPOs that are controlling the redirected content to focus on the new location. We will also remove the DFS replication and Namespace so we can decommission the Windows Server 2003 R2 box.

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.