News Stay informed about the latest enterprise technology news and product updates.

Major Windows Server Hump Ahead: WS2003 EOL on 7/15/2015

In researching a story for SearchWindowsServer late last week, I came face-to-face with some horrifying numbers. The first is a set of statistics from various sources that indicate more than 10 million servers are still running Windows Server 2003 in production mode in companies and organizations around the world (see, for example, these discussions in Redmond Magazine and in Greg O’Connor’s AppZero blog). The second is the looming date for end of life for that same software on July 15, 2015, where EOL is defined as the “day after Microsoft terminates extended support” for that OS version. You can look this up for yourself at the Microsoft Product Lifecycle Search page, where keying in “Windows Server 2003 R2 Standard x64 Edition” produces the following results (remember: the Extended Support End Date precedes EOL by one day):


I deliberately focused in on the most popular WS03 version to produce a tiny table.
Searching on “Windows Server 2003 R2” instead will cover the whole product family.

Turns out there’s lots of work to do to prepare for a server migration — some of the most important aspects of which I’ll document in my upcoming SearchWindowsServer article for Techtarget (I’ll provide a link to that story right here as soon as it goes live) — so I’m simply stunned to realize that somewhere around 10 million servers in need of migration are still up and running some version of Windows Server 2003 right now.

If this applies to you or your organizations, it’s past time to get going on migration planning. Even with the end-of-year holidays almost upon us, somebody needs to get to work immediately on planning for this effort. The biggest stumbling block is likely to be application compatibility, according to those companies, organizations and enterprises who’ve already been through the exercise. With seven months left to go before the EOL date hits, that doesn’t leave much time to analyze compatibility issues and implement changes, workarounds, or replacements for the applications that so often provide the rationale for using servers in the first place.

If there’s a silver lining to this story, the necessity for change comes with two powerful potential improvements. First, it makes sense to rationalize and consolidate physical Windows Server 2003 server installations in some kind of virtualized form (which means some kind of hypervisor based virtual server environment, or some kind of virtual container for same). Second, it may also make sense to move those virtualized (and consolidated) servers that survive the migration process into the cloud. This will involve considerable work, certain expense, and solving numerous interesting and perhaps even challenging technical problems. But with the end of Windows Server 2003 now clearly in view, hopefully migration will also provide the opportunity to improve and strengthen IT operations along the way.

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

AND....W2K3 and WinXP do not support IPv6 - fully (no W2K3 server services support it - DNS, DHCPv6, AD, etc)...a basic IPv6 protocol stack can be installed, but Microsoft really viewed it as "proof of concept" for networks that want to/need to add IPv6, they have to migrate OS's more reason to do it!

Good point, Jeff: thanks for mentioning this. 2003 was far enough back that nobody felt *compelled* to support IPv6. Today, of course, that is no longer true, and MS offers an implementation that is as good as anybody else's (and better than some).

Thanks again,


Just got an email asking if anybody really uses IPv6 and, by implication, if anybody should care about it at all. IPv4 addresses are now officially "exhausted" and all new networks, especially big ones, are pretty much bound to use IPv6 going forward. This is especially true outside North America, where most major network deployments are IPv6 exclusively nowadays. Still not convinced? Take a look at who's playing with/using IPv6 on the World IPv6 Launch "measurements" web page: