Need to migrate Windows Server 2012 to a Server 2019 / 2022? This tutorial will show you how.
Server 2012 R2 End Of Support is October 23, 2023 – so, naturally, you are not alone: 2012’s should be migrated ASAP. Of course, you want to minimize the time and effort spent on that, and to automate as much of that migration as possible.
In this guide, we’ll cover how to natively migrate server applications, databases, user profiles, shares, data from Server 2012 / 2012 R2, to a new Server 2022 / 2019. We will also cover role migration best practices and tutorials. (Note: this works for non-2012 servers as well, we are just focusing on 2012 due to its 2023 EOL)
Migration covered here is native migration – not app virtualization. You can use these methods to migrate from physical to physical, physical to virtual / Cloud, Cloud to Cloud etc. For example, you can migrate from an on-prem physical 2012 to an on-prem 2022 VM, from an on-premise Server 2012 to an Azure Server 2022, or from a Private Cloud 2012 R2 server to an EC2 Server 2019.
The goal of this how to is to allow to complete a server migration in less than 4 hours for application and file servers, and less than 24 hours for role-focused servers (although complicated cases may require more time).
Just want to find out how to automate the migration, and don’t need a general tutorial?
Click here to skip to the part with the actual migration process.
Or, if you need to migrate workstations, click here for migration to Windows 11.
WinServ is also available from IBM Services, as part of their full service package for large scale deployments. Contact your IBM account team in your region for more information.
Audit your servers: In a typical environment, you’ll have quite a few different server types. There will be role-oriented servers, which focus on Windows Server roles such as Domain Controller, Active Directory, IIS, Exchange, DNS, DHCP. The more common group, however, are application and file servers, which run the actual Line of Business applications (LOB) and store the company data. They typically outnumber the role-based group.
Migration is done differently for these two. Roles are migrated manually, or with utility tools that are typically focused on one specific role (see below).
Application and file servers, however, can be migrated automatically and on massive scale, using server migration software such as Zinstall WinServ.
In the planning stage, you need to prepare a list of servers in the environment, and figure out what each of them is responsible for.
Even just knowing how many role servers and how many application servers is already a big step. Since application server migration can be automated, you will be able to develop a fairly accurate estimate of time and effort that will be required for the migration.
Schedule your migration time slot: Migrations take time, and during that time, your users may be affected to some extent. If possible, try and schedule the actual migration to be performed after hours or during a weekend. Note that you don’t actually have to stay there yourself at that time: application migration can be performed remotely or launched in advance in unattended mode.
Verify your backups are up to date, and are actually restorable: Any major upgrade may go wrong, and without a valid up-to-date backup, you risk losing everything you’ve had on the server. Make sure to verify that the backup you have is not damaged and ready to be restored if needed!
Decide on replacement type: Once you have decided to replace a server, you have several options regarding what the replacement will be. It may be an on-premise physical Windows 2022 / 2016 server, a on-prem VM server (ESX / Hyper-V, for example), or a Cloud-based server running off premise (such as migration to Azure or migration to Amazon AWS). If you are using WinServ, it supports any of those transfers, so migration difficulty does not vary significantly with your choice.
The process below outlines the migration steps for moving from Server 2012 / 2012 R2, to a new Windows Server 2016 / 2019 / 2022.
Option 1: Direct migration from 2008 to 2022 / 2019 over network
Option 2: Indirect migration, via intermediate storage
This part of the migration is done manually, and multiple tutorials exist that may help. We recommend John Savill’s excellent guide: Winding Down Windows Server 2003 in Your Organization. Information below is based on the article above.
Some legacy 3rd party applications running on Windows Server 2012 may be incompatible with Windows Server 2022 / 2019. This is not as common as it once was with Server 2003 / 2008, but it may still happen – usually for legacy software, which has not been updated for newer OS versions.
Note that “old” does not necessarily mean “won’t work”. Quite a few applications ah
If these applications cannot be eliminated immediately, and are mission-critical for continued operation of the organization, the recommended option to preserve them operation is to perform a virtualized migration of those applications, into a virtual Server 2003 instance running on newer replacement server. Then, continue to take the steps required to phase those applications out and stop running the virtualized 2003 instances.
WinServ is application-generic, and can migrate even custom and in-house applications that have not been seen by the outside world – as long as they are capable of running on the new server. Here is a partial list of common applications that our customers have migrated in the past:
Once the migration process is complete, it is time to verify the results.
Congratulations! Your server migration is now complete.
Ready to migrate to Windows Server 2022 / 2019 / 2016?
You can also contact us for assistance, volume licensing, and help in setting up a POC.