2010 will be here in no time, and with it will come some changes to support for Windows Server. In July 2010, public support for Windows 2000 will cease. At the same time, Server 2003 moves from mainstream support into the “Extended Support” phase. While security patches will still be released, all non-security hotfixes developed during this period will be restricted to customers enrolled in the extended hotfix support (EHS) program.
To many this came as a shock, given that there is less than 10 months left until July is upon us. While many hotfixes address issues that impact a small subset of installations, others have a more widespread influence, and banking on not needing any hotfixes is a sure recipe for “rush upgrades” after July 2010. As illustrated by the end of Server 2000 support, even security patches will stop at some point, so there is no better time than now to start devising a migration/upgrade strategy for your Server 2003 systems (and perhaps more urgently, your Server 2000 systems!)
Obviously this change has consequences for lots of services and applications, in addition to just the operating system. For example, some applications have a specific operating system requirement (and support contracts may require this to remain valid), or simply don’t yet “officially” support Server 2008. Start talking to your application vendors and obtain commitments for support. Nothing lasts forever!
To read the full announcement issued by the Windows Server Division, click here.
Comments
Interesting stuff. I didn't realize the change was going to have that kind of impact. What are your thoughts about that?
Steven,
I've brought this up several times with people since writing the post, and the typical reaction has been "what? really?". Even with only nine months to go (one down already!), there is still time to assess the importance of systems if such internal classifications don't already exist, and prioritize upgrade plans accordingly. Entering EHFS doesn't mean everyone will need/want to upgrade every system, however for mission critical apps, it's probably a good idea to assess just how critical hotfix support is.
For many, it will be unrealistic to plan on having every system and and application tested and upgraded to a 2008 platform by July of next year. However, there is plenty of time to plan and upgrade select mission critical systems in a managed fashion, for which hotfixes and ongoing non-security support are deemed critical.
This leaves other systems running on a platform that is certainly mature, and likely to function in an acceptable manner without necessarily needing hotfixes. It does serve as a salient reminder that after July, the next support change will be the end of security patches as well.
Policy-wise, now would be a great time to clearly state that new Server 2003 deployments should not be entertained without clear justification warranting an exception, and that rebuilds and hardware refreshes should also include a 2008 upgrade if possible.