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

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

Last week I delivered a Windows Server 2012 R2 class in Fort Wayne. I had a real neat idea from the class pop up during the Distributed File System (DFS) content. The class member’s situation was that he had over a terabyte of user home folders and redirected folders on a Windows Server 2003 R2 box and needed to move it to a Windows Server 2012 R2 box with minimal, if not zero, disruption to his 24-7 organization. DFS sounds like a good idea, but would the two versions of DFS work together?

This is part 1 of a 3 part series on how we accomplished this task.

We started off with this configuration:

Our general process looks like this:

· Install DFS Namespace and replication on both servers (S1 and S2).

· Create a DFS Namespace on S1 that has references to both shares.

· Create a DFS Replication Group between S1 and S2.

· Change the GPOs to point to the new server.

· Disable S1 and verify that the clients are using S2.

· Bring S1 back online and remove the Replication.

· Remove DFS from S2.

In all honesty, the hardest part of this was trying to remember how to install Windows Server 2003. We struggled a bit to get it right. I may be an MCSE on Win 2003, but it has been a very long time. After we got the cob webs between my ears cleared up, we went to work.

Install DFS on S1 (Windows Server 2003 R2)

Insert the Windows Server 2003 R2 DVD (Or ISO file) in the DVD drive.

Click Start à All Programs à Administrative Tools à Manage Your Server.

Click Add or remove a role.

In the Configure Your Server Wizard, click Next.

On the Server Role page, click File Server à Next à Next.

In the Add File Server Role Wizard, click Next, and then click Replicate data to and from this server.

Follow any on screen instructions and then reboot the server.

Install DFS on S2 (Windows Server 2012 R2)

Open Windows PowerShell as an Administrator

Type (This is one continuous line):

Install-WindowsFeature -Name FS-DFS-Namespace,

FS-DFS-Replication -IncludeAllSubFeature -IncludeManagementTools -Restart

Tomorrow, we will add in the DFS Namespace and replication.

Comments

Sticky Key problem between Windows Server 2012 and LogMeIn

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 .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog