Financial institutions and ATM deployers are no strangers to large-scale operating system migrations. Within the past decade, organizations have had to migrate from OS/2 to Windows CE/XP, and then on to Windows 7. Now, in a few months’ time, on Jan. 14, 2020, Microsoft will no longer provide regular technical support, security upgrades, or patches for devices running Windows 7 if they are not on extended support. Needless to say, this ATM software update can leave your fleet vulnerable to cyberattacks, as well as fees associated with PCI noncompliance.
If you’re an independent ATM deployer, you’ve likely had Jan. 14, 2020 on your mind for quite some time now. Believe it or not, that date—which is when Microsoft will no longer provide technical support, security upgrades, or patches for Windows 7—is coming faster than you think. And if your fleet isn’t on its path to a Windows 10 migration when it does, your organization’s compliance, security posture, and functionality options might be severely impacted.
With all of the buzz around the deadline to move to Windows 10 by January 14, 2020, in the news and in the headquarters of financial services companies, it makes sense why some could be considering alternatives to their current operating systems.
Believe it or not, January 2020 is just around the corner. And if you operate some of the estimated 3.5 million ATMs running on Windows 7, that date is a big deal. While at first blush, the migration seems straightforward, there are a number of considerations that need to be addressed to help make the transition of your fleet a successful one.