A guide to Windows Server 2003 end of life
Editor's note
With Microsoft ending support for Windows Server 2003 on July 14, 2015, the time has come for users to migrate to a new server.
This guide will help you prepare to move away from Windows Server 2003 and avoid any problems during the process. It will also look at some choices for a new server, including Windows Server 2012 and Windows Server 2012 R2.
1Prepping for a Windows Server 2003 migration
Now that you've decided to migrate from Windows Server 2003, it's time to prepare for the process, get the wheels in motion and avoid common mistakes.
2Moving on to Windows Server 2012 or Windows Server 2012 R2
For enterprises that have chosen to skip over Windows Server 2008, the next best options are Windows Server 2012 or Windows Server 2012 R2.
-
Article
Is it time for your enterprise to migrate to Windows Server 2012?
If your enterprise has plans for a large-scale virtualized environment, a Windows Server 2012 migration might be a good choice. The OS features an enhancement to Hyper-V called Replica, which provides continuity with disaster recovery sites. Read Now
-
Article
Steps for migrating to Windows Server 2012
Once you've decided to migrate to Windows Server 2012, the first step is to ensure that your hardware meets the minimum requirements. You'll also want to upgrade your system's ROM and update miniport drivers and their corresponding firmware. Read Now
-
Article
Windows Server 2012 R2 upgrade prep
To avoid issues during an upgrade Windows Server 2012 R2, consider testing upgrades and rollbacks in the lab first. Performing full backups of each server and virtual machine will also mitigate any losses in case the upgrade fails. Read Now
-
Article
Migration options for Windows Server 2003
Organizations are considering Windows 2008 or Windows 2012 upgrades, along with the option of choosing a cloud deployment, when moving off of Windows Server 2003. Read Now
-
Article
Benefits of a Windows Server 2012 migration
With an improved Server Core, as well as an additional 2,300 cmdlets in PowerShell 3.0, Windows Server 2012 may be a good fit for enterprises that want to get more from their server hardware. Read Now