I spotted this last week, but this is with a more local focus.
This is a key risk for organisations that choose to:
a) Run a closed source package which leaves them at the whim of the vendor; and
b) Run a Windows based system without allowing for updating to a 'current' generation OS.
Windows 2000 is closing on 10 years old (obviously) and most people have moved to Windows XP or Vista (on the desktop) or Windows Server 2003/2008 (servers). Those who havn't are either poorly organised or have a particular reason for staying with Win2k; perhaps compatibility with hardware or a particular software package.
However these people are now left without an option for the security of their system, thanks to the Vendor deciding 'no' (this despite the fact that I read somewhere, MS had previously agreed to keep patching the OS until next year!)
It brings me back to one of the reasons Im becoming a big fan of the open alternatives; The decisions of a profit-focussed monopoly vendor should not be allowed to have such potentially far-reaching effects.
Me thinks those with remaining W2K machines will be working to replace them fast - or isolate them behind a suitably configured firewall... I hope however this is something of a learning experience!