According to Microsoft, it wasn't feasible to build the fix for Windows Server 2003 because it would have required re-architecting not just the Group Policy component, but also other significant parts of the operating system. Such big architectural changes could have created incompatibility issues with applications that were designed to run on Windows Server 2003, the company said.
While the explanation sounds reasonable, it's likely to be of little comfort to companies who were still expecting to receive Windows Server 2003 security patches until July -- and even beyond in the case of those who plan to pay for custom support.
There are still millions of systems running Windows Server 2003 worldwide and analysts predict that migrating them to newer OS versions will be difficult, because an entire business software ecosystem has been built around the aging OS.
Sign up for CIO Asia eNewsletters.