Skip to main content

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

By

We are in the home stretch!

Over the past two days we have configured DFS on both Windows Server 2003 R2 and Windows Server 2012 R2. Re have replicated out data and we are now ready to start the process of decommissioning out old server.

Change the GPO to point to the new server and the new folder paths

Once you are confident that replication has occurred and completed successfully, you can now modify your GPOs to point to the new server. Clients will continue to use the old server until they are using the new GPO. The DFS Replication will make sure their data is moved to the new server.

Open Group PowerShell management Console.

In the GPO that controls the user profiles, open:

Computer Configuration à Policies à Administrative Templates à System à User Profiles

Open Set User Home Folder

Change the server in the UNC to the new server.

image

Click OK, and close the GPO.

Open the GPO that controls the file redirection

User Configuration à Policies à Windows Settings à Folder Redirection

Right click the folder where redirection is occurring and select Properties

Change the server in the UNC to the new server.

image

On folder redirection, click on the settings TAB.

Uncheck Move the contents of Documents to the new location.

image

Click OK

Click Yes

Close the GPO.

Allow plenty of time for replication to all clients. Group Policy replication is a funny thing. It is a patience driven activity. Depending on your environment, this can take hours to days. If you are in a domain with many sites, error on at least a day. Also, your clients many need to go through a few reboots before these policies take effect.

You can verify redirection on your clients. To do this, log in to a client machine as a user who would be affected by this change.

Click Start and then click File Manager

image

Right click Documents and select Properties.

Look for the location to change to the new server.

image

If this does not happen, verify that the share permissions were set correctly on the new server.

Take S1 offline and then test

Take the original server offline for a few days and make sure everything works OK.

When you are ready, bring S1 back online and allow replication to finish.

Remove DFS Replication

On S2, open the DFS Management console.

Expand Replication.

Right click UserInfoRepGroup and select Delete.

Select Yes and then click OK.

Once you are satisfied that everything is OK, you may remove DFS from S2.

Finally, this is our configuration:

image

Labels:

Comments

Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

How to list all the AD LDS instances on a server

By
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.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more