November 21, 2026
placeholder

By Colin Dennis, OGL Computer, Head of Internal Operations at OGL Computer Services Group Limited

Products and services become obsolete, and businesses using technologies such as Windows, need to plan for End of Life (EOL). In this article, we explore the key considerations when transitioning from soon to be obsolete technologies, and how the right planning can ensure a smooth transition.

A business faced with an upcoming EOL must consider a number of factors – how to implement that response, mitigate risks, choose which product or service to go with, how it’s going to affect the running of the business and the staff, and how to limit damage in any worst-case scenario, all while juggling the usual IT tasks, advising other departments and dealing with technology issues.

While versions of Windows 10 and 11 are becoming obsolete, we’ve decided to take Windows Server 2012 as our example. In just over 18 months’ time, on 10 October 2023, it will reach the end of a 10-year product lifespan. Reaching EOL doesn’t mean a product will simply stop working on that date – organisations using Server 2012 could continue to use it for years to come. However, using products beyond their EOL date can create serious risks.

Windows Server 2012 represented an historic advance for internet-based infrastructure: it was the first server operating system to integrate extensive cloud functionality. Most enterprises using Server 2012 are computer software and IT-oriented businesses, but the OS sees significant use across all areas. Small- and medium-sized enterprises (SMEs) are the primary users of Server 2012, with approximately 70% of its customer-base being SMEs.

Effective EOL planning requires organisations to have an active knowledge of all operation-critical products and their EOL dates. Each business must evaluate its options for replacing the EOL product. The supply chain should also be examined as thoroughly as possible, to prepare for any disruption to partner organisations caused by EOL transitions. Perhaps most importantly, robust failsafe planning and disaster mitigation should be put in place to account for loss of functionality during the EOL period.

Mapping the road ahead

One of the most effective planning strategies for any business facing End of Life technology is the IT roadmap. Roadmaps provide a flexible and accessible means of long-term planning and allow management to coordinate the different arms of the organisation with minimal disruption.

This requires commitment, work and cooperation to be effective. Creating an effective IT roadmap is like solving an intricate puzzle, and it needs every division of the business to be prepared to coordinate around significant events. EOL dates, changes in regulation, new technology and marketplace fluctuations will all affect the roadmap, and it must account for the whole process of every internal response to external changes. When a roadmap works and is well-maintained by the business, it improves day-to-day productivity and allows the enterprise to meet EOL dates and any other obstacles well-prepared.

The benefits of IT roadmaps are extensive, but so are the challenges. OGL has experience maximising the benefits and overcoming the challenges. By using a long-term roadmap strategy, OGL was able to assist Motivair to modernise and future-proof its IT infrastructure for years to come. Creating this roadmap required the depth of expertise and dedicated work that could only come from third-party industry experts who are able to ask questions about the business’ future that less dedicated service providers weren’t asking.

Windows EoL and moving forward

Updating or replacing any business-critical product that hits EOL is daunting and usually costly. If the transition is made haphazardly or without thorough planning, it can severely disrupt business operations in the short-term and lead to serious problems further down the road. Any IT manager or executive could be forgiven for taking a ‘don’t fix what isn’t broken’ attitude at first glance.

However, simply letting things drift is guaranteed to cause critical problems sooner or later. With Server 2012, these would likely revolve around:

  • No further security updates for WS2012 at all. After EOL, Microsoft will no longer be offering patches or updates, even if new critical security vulnerabilities are found. Any newly discovered vulnerability is, and will remain, a zero-day vulnerability. Hackers will specifically target organisations running vulnerable EOL products, which will have become easy targets.
  • No technical support for critical errors. During the first five years of a Windows Server product’s lifecycle – the Mainstream Support phase – Microsoft continually release updates that include new features, service packs, fixes and patches. During Extended Support, up to ten years after the initial release, the product is no longer the focus of the Microsoft team and new products are likely to have launched which supersede it. Only critical security updates and patches will be developed by Microsoft.
  • Incompatible software. Even though an EOL product may still be technically functional, new products and services will no longer be developed to be compatible with it. This can severely limit an enterprise’s options and ability to respond to market changes going forward.
  • Compliance issues. GDPR, and other privacy regulations, require businesses to take reasonable efforts to secure personal data. It’s also a key criterion of the Government-backed Cyber Essentials certification to have operating systems (and also software, devices and apps) that have their vulnerabilities patched. As EOL products are known to be significant security risks, a business that fails to find an adequate replacement and then suffers a security breach is likely to be deemed negligent and penalised heavily by privacy regulations.

 

These factors leave no doubt that an impending End of Life date is not something an enterprise can afford to ignore, but it’s easy to feel completely lost at sea – especially if the business’ server solution is something that has ‘just worked’ for years. Moving on from any EOL product leaves IT management with a much more complex task than just updating to the next server iteration.

An IT roadmap is the best solution but creating and maintaining a comprehensive and well-planned roadmap while trying to keep a handle on so many other aspects of running the IT department is a tall order. An outsourced IT consultancy service offers a way for a business of any size to streamline the process of preparing for, and traversing, an EOL date.