A lot of IT administrators probably wake up each morning, look at the calendar, and sigh. That’s because there’s only three months and change left before January 14, 2020 – the day that Windows 7 is officially end-of-life.
If you work in information technology, you probably know that when a piece of software is declared “end of life,” its end is in reality far from over. If you’re still running a copy of Windows Server 2003 – like one in five companies as of 2016 – then you’ll get the idea. Same if there’s a computer in your organization that still runs Windows XP. Although less than 5% of companies still run Windows XP, a majority of ATMs still do.
For many companies, upgrading operating systems across the organization can be a complex challenge. Application and driver compatibility are two variables among many that must be thoroughly analyzed to successfully deploy windows upgrades.
Comprehensive analysis of the technology landscape can be frustrating and time-intensive, but if the proper planning is not completed, then less than desirable outcomes are often achieved.
Generally speaking, companies must weigh the pros and cons of upgrading or updating any system. It is accepted that physical assets such as machinery or equipment must be maintained at specific intervals.
Furthermore, the projected end of life date is typically established at the time of purchase. Equipment kept in use past its projected EOL requires additional maintenance and upkeep and often hampers productivity or increases risk and most companies would not dispute this fact.
Software systems are no less critical. Software applications and operating systems also have a projected EOL, but often the temptation to extend the service life of these assets is greater than for a piece of equipment that you can touch and feel.