So, if you really want to do something cool in your migrations you should use DFS Replication. With Distributed File System Replication we create a DFS share that includes the shares from the Source Server and the Destination Server. We then set a replication schedule. Tip! Before you continue with the migration of your files and folders to your Windows Server 2016 or 2012 Essentials make sure you have moved the location with the wizard from the Dashboard. If you use your server without the Essentials Experience role this does not apply. 1. How to setup replication between the Source and Destination server In this example we have a SBS 2011 that is already no longer the PDC in the network, all roles are migrated to the new Windows Server 2012 R2 (Essentials) and the SBS has been demoted. The SBS 2011 is now a normal fileserver that still holds the shares that were previously created. We can check this by running ‘net share’. On the Destination server start the Server Manager and in Tools click DFS Management. If you do not see that you need to install that first with Add Remove Roles and Features. In this example our Destination server is a Windows Server 2012 R2 Datacenter with the Experience role installed but it is the same for Windows Server 2012 R2 Essentials. The Source server is called ADATUMSERVER and the share we want to replicate over to the new server is called “\\adatumserver\RedirectedFolders”. That share contains all redirected folders. Choose New Folder as in the screenshot. I choose to name this DFS Share ‘Redirected Folders’. Click ‘Add’. Click ‘Browse”. Choose ‘Folder Redirection’. This may be confusing for you but this is actually the Folder Redirection share on the Destination server. Click OK. Click OK. Now we need to add the other share that will be a replication partner. Click Add. Click Browse Fill in the name of the Source Server, click Show Shared Folders and choose the Shared folder you want to use as a replication partner. Click OK when you are done. Click OK. We have now added two folder targets and click OK. The wizard asks us of we want to create a Replication group, click Yes. Accept the defaults and click Next. Click Next. Choose the Source Server as the primary member. In our case that is the ADATUMSERVER. Choose Full mesh and click Next. We can choose to replicate only during the night and in the weekends. Choose Edit schedule. Create the schedule that fits your needs and choose OK. Click Next. Click Create If all checks are green click close. Click OK. Replication is now setup and will start to work according to the schedule we just set. Depending on the amount of data and the performance of your servers and network this may take several hours or days to complete. You can create a diagnostic report to see the status of replication. During this stage clients will remain to connect to \\SourceServer\Sharename but you can also choose to connect to \\DestinationServer\Sharename even if replication is not completed. Users will never notice anything about this procedure. After replication is completed you can break the replication by either removing one partner or by deleting the replicated folder in DFS Management. 2. How to create diagnostic reports When you have a lot of data I suggest you let replication run as long as you can but at some point you want to know the status. Here is how you create diagnostics reports and read them. Click Create Diagnostic Report Choose Health Report Next Next Check ‘Count the replicated files and sizes of each member’ and click Next. Now this can be confusing if you see such a report the first time with all those warnings but in most cases they don’t mean much. It warns you DFS replication has been restarted 5 times in the past 7 days…big deal. Seems to be some thresh hold in the logic that builds these reports. More important is that you check for staging errors. Those can occur if the files you want to sync are big. In that case you need to increase staging size, see Edit the Quota Size of the Staging Folder and Conflict and Deleted Folder for more info on this subject. 3. How to stop replication and remove shares and partners One you are done you need to remove replication because the old Source server like an SBS 2011 or 2008 must be removed completely from your network once it has been demoted. Why? You are not allowed to use a SBS any other way it is described in the EULA. Right click the folder you created for replication. Click Yes and you are done. If you still see the Folder under the namespace right click again and delete. It just removes the folder from the namespace, nothing else. Click Yes.