Running Windows Server 2003 in a Post-Support World
You’ve heard it said — “All good things must come to an end.” And with the end of support for Windows Server 2003 on July 14, 2015, the logical conclusion is it’s time to upgrade to newer, supported, flavors of Windows Server. While most organizations have focused efforts around moving off of Windows Server 2003, not all of you are either ready to do it, or are more simply put — can’t do it.
You’d think having been given enough warning, it would merely be an issue of planning and execution to move to, say, Windows Server 2012. But, given the average migration timeframe is 200 days, according to Microsoft, it becomes obvious that it’s just not that simple.
With an estimated 9 million installations of Windows Server 2003 still existing months before the deadline demonstrate that organizations, like yours, have their reasons for remaining on this 11 year-old operating system. Budgetary constraints always come into play, as running Windows Server 2012 will not only require new licensing, but also new hardware. The inability to migrate off of critical applications that are no longer supported, have no current version, or have no equivalent replacement are reason enough. And then there are simply organizations with smoothly running instances of Windows Server 2003 where the age old “if it’s not broke, don’t fix it” adage applies.
But, without support, is it really not broke?
Read the entire white paper here.
Client: Bit9 + Carbon Black
