But if you’re prepared to move workloads to the cloud, you get a little more flexibility. The release of Windows Server 2022 is a good reminder that older versions of the OS will be losing support and security updates soon, along with older versions of SQL Server. Image: Shutterstock/Khakimullin Aleksandr Here's why you should be thinking about 2012 migrations now as well. The only way to get extended support for 2008 versions of Windows and SQL Server is in the cloud.

If both DFS servers are Windows 2008 R2 then you can now disable the old server in the DFS Name Server list using the DFS Management Console, if one of the servers is running a previous version of windows not proceed to step 10.It’s time to get off Windows and SQL Server 2012 (or run them on Azure).

Again, wait for AD DS replication to ensure that the additional server is listed on DFS clients (use dfsutil /pktinfo to verify).

Set referral order override configure the new server as “First amongst all targets” and the old server as “Last amongst all targets” using the DFS Management Console.

Wait for AD DS replication to ensure that the additional server is listed on DFS clients (use dfsutil /pktinfo to verify).

Add new server to DFS Namespace(s) that you have replicated the data for using the DFS Management Console.

Before proceeding make sure that all data is replicated. For fairly static data the last two are fine, for data that changes more frequently I would choose DFS.

Replicate the data, either using DFS, RoboCopy or SecureCopy.

Create SMB shares on the server that you will host the DFS Namespaces from.

Install OS and configure the server that you will move the DFS namespaces to.

I recently used the steps below to move DFS Name Spaces from one server to another without interruption to client connectivity. Windows Server : A simple DFS Migration Plan

Migrate lansweeper to new server