Windows Server 2003 EOS

The Problem:

Windows Server 2003 is fast approaching its end-of-life. Microsoft has announced the official date for end-of-life support as 14th July, 2015. While many administrators are well aware of this fact, there are still vast numbers of servers across the globe running live applications on Windows Server 2003.

It should be cause for alarm that so many businesses are still reliant upon an operating system originally released almost 10 years ago (December, 2005 for Windows 2003 R2). More concerning is that many of these W2k3 servers are running applications originally developed for a 32-bit operating system.

Even if your Windows 2003 server is stable at this time, do you want to risk running your applications on a server that will not ever again be supported starting July 15, 2015?

Consider also that almost all hosting service providers will ultimately force their customers to migrate to newer, fully supported platforms so that they can continue to provide the support – and security – promised in their service level agreements, which will not be possible once the Windows 2003 server OS is officially unsupported.

Businesses in industries where sensitive data is handled and compliance is a key requirement may find that they are out of compliance, which could mean fines or being cut off from trading partners.

The problem with a last minute migration approach is when the server/version upgrade results in problems, errors or inconsistencies with security, stability or functional issues with your applications that require immediate remediation, and most often programmatic revisions.

Needless to say, waiting until the last minute to perform your Windows 2003 server migration is a risky proposition.

Windows Server 2003 End-of-Life Server Options

There exists an understandable (but unwise) reluctance to migrate from a currently stable Windows Server 2003, likely due to fear of the inevitable challenges that administrators and developers may encounter with incompatibilities (especially between 32-bit and 64-bit platforms).

Although some migration tools can aid the migration of some applications/websites, most services still running on Windows 2003 servers are fairly custom and will present unique, specific challenges during migration/version upgrade.

Therefore, a best practice to prepare for your migration is to start with a thorough migration and upgrade plan well in advance of the end-of-life date, for the reasons we have stated here.

Your Options

1. Stay Put.
In this scenario, you no longer require server support, are prepared for major vulnerabilities and are perfectly fine to just “kick the can down the road.”

Assuming you actually rely on your Windows 2003 server applications, this option is only viable if you already are underway with replacing all your applications and servers with a new architecture from the ground up.

2. Upgrade The Server.
Performing an upgrade to your existing server, if even an option, in most cases will result in functionality errors with your applications that you’ll need to resolve in a “live” environment. Moreover, it’s likely the server itself is several years old (or more), so you’re solving one problem in a potentially reckless, short-sighted manner while leaving the legacy hardware issue for a later date, compounded by having to diagnose and resolve application failures (at an unknown magnitude of time and expense) in your live environment.

3. Migrate and Upgrade.
In most all cases this is your best, most logical option. Start with your plan, and start now.

Best practice planning for your Windows 2003 server migration should include phases for project scope (technical and project management), resource allocation, capability (i.e. programmers and testers) and budget. There are more granular components as well, but these are a good place to start.

If you need any assistance or have any questions about migrating from Server 2003, please get in touch on 023 81 61 71 81.