Jason Yoder, MCT

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. Click OK , and close the GPO. Open the GPO that controls the file redirection User Configuration à Policies à Windows Settings à Folder Redirection

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 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 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 \\

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. ·     

Every once and a while, a good mystery can be fun.  For IT Professionals taking a class, not so much.  During my last PowerShell class, one of my students made an observation in a help file.  The Cmdlet in question was Set-ADUser . Take a look at the help information on these two parameters. -Identity <ADUser>         Specifies an Active Directory user object by providing one of the following property values. The identifier in parentheses is the LDAP display name for the attribute. The acceptable values for this parameter are:                 -- A Distinguished Name         -- A GUID (objectGUID)         -- A Security Identifier (objectSid)         -- A SAM Account Name (sAMAccountName)                 Required?                    true         Position?                    1         Default value                        Accept pipeline input?       True (ByValue)         Accept wildcard characters?  false -Identity <ADUser>         Specifies an Active Directory user object