After a 12 year run, Microsoft is finally set to withdraw extended support for the Windows Server 2003 family of operating systems. After 14 July, Microsoft will not provide any patches, updates or support to businesses using Server 2003 unless they take out an extremely expensive custom support agreement.
In the event that your business does not have a spare $9 million (or access to public funds), the only cost effective option available is to take the leap and upgrade to one of the two more recent versions of Server – 2008 or 2012. But only a few days until the deadline, what do you need to do to be ready? This checklist will take you through the most important steps required to complete a successful migration.
1. Assess your upgrade options
Chances are that your direct upgrade options are severely limited if you are still using Windows Server 2003 because the hardware simply will not handle the demands of a later version. Even if you can coax an upgrade to Server 2008 you must decide whether the effort and relatively short remaining lifespan of the OS outweigh the benefits of buying an upgraded system capable of running Server 2012.
Use this handy guide to find out more about the different upgrade options you have available.
2. Assess your migration options
In all likelihood you will need to purchase a brand new server and migrate data and settings from the original machine. It is important to note that Microsoft does not provide an automated upgrade tool for moving from Server 2003 to Server 2012.
Instead you will need to perform a double upgrade (2003 to 2008, followed by 2008 to 2012) or more likely, a manual migration between the two versions. For the rest of this guide we will assume you are migrating software, services and files to a completely new system running Windows Server 2012 R2.
3. Purchase the relevant hardware and software
As well as choosing a system capable of running your chosen server operating system, you need to identify one that will support your current data needs and provide capacity for the future. Ideally you want your server to last as long as possible if it is to provide maximum return on investment.
Define which roles the server will perform and seek professional advice from your systems reseller if you are unsure of exactly what you need.
The first practical step for any activity that has the potential to radically alter your system is to take a full system backup. Do not do anything until you have a full, working backup.
5. Check the backup
Double and triple check your backup – this is your only way back should something go wrong during the migration to a new version of Windows Server.
6. Setup the new server
Assuming the Windows Server 2012 R2 operating system has already been installed on your new machine, connect it to the existing Server 2003 network and power it up. Otherwise you need to carry out the basic OS installation first.
Because none of the settings have yet been configured on the new server, it will not interfere with the existing network or domain.
7. Familiarise yourself with what comes next
There are a number of steps involved with manually migrating from Server 2003 and you should familiarise yourself with each before proceeding. Make sure you fully understand what is involved, and that you have sufficient support in place before you proceed.
TechNet has plenty of material to cover the process, but Canadian IT Pro Connection has a much more succinct explanation of the Windows 2012 R2 migration steps that saves clicking through dozens of pages on Microsoft’s site.
8. Dispose of your old server safely
You may choose to keep your old server handy just in case a problem occurs within the first few hours or days after the migration. However once you are sure that everything is correct, you should arrange for disposal of the computer in line with the EU WEEE directive, confirming that any data has been erased using secure file shredding software or a Degausser to prevent recovery by unauthorised third parties.
Migrating from Server 2003 to Server 2012 R2 is undoubtedly tricky and time consuming. And although Microsoft withdraws support for the OS on the 14th, everything should be fine if you need to delay your migration for another week or two while you thrash out the details of the project. Just don’t fool yourself into thinking that an upgrade/migration is unnecessary.