As with all things related to technology, change and evolution are inevitable. End of Life (EOL) is part of a typical technology lifecycle and means an application, platform, or hardware will no longer be supported by its manufacturer. No more patching or security, no more updated versions. Choosing to continue to use an application, platform, or hardware once it has reached its end of life can result in compliance issues, increased operational costs, and, as mentioned above, security issues. Therefore, it is best to approach EOL strategically as part of your technology roadmap.
End of Life Management
There are three steps to effectively managing EOL:
1. Approach Proactively
2. Understand your Options
3. Communicate Changes
Approach End of Life Planning Proactively
As mentioned above, you do not want to let an EOL for a critical application, platform, or hardware catch you off guard. Many EOL dates are set more than a year in advance allowing your organization to build a strategy around replacement.
With supply chain disruptions becoming commonplace in the past two years, it is more important than ever to order hardware in advance.
Understand your Options for Alternatives to End Of Life
Perhaps this EOL situation provides an opportunity to upgrade or perhaps your organization will stick with the newer version of the tried and true. Take time to decide if the product supports your organization’s goals as well as it should or if there is a better solution available. Understanding all of the options can feel overwhelming, but it’s not a decision you have to make alone. A managed service provider like GadellNet can give you insights and guidance.
Communicate Changes relating to End Of Life
Your employees will surely be impacted by EOL, even if it is just a cut-over performed during off hours. Being transparent and giving everyone time to plan for the changes ahead will ensure there is less resistance and fewer bumps in the road.
To help stay ahead of potential lead-time challenges and budget changes, we have compiled a list of relevant applications, platforms, and hardware with recent and near-future end dates.
|Important Information & Next Steps|
Mac OS Mojave
|Using an OS that is no longer supported eliminates your ability to receive important OS service and security updates. We highly encourage end users to upgrade when possible or replace unsupported hardware. Mojave went EOL on 11/30/21.|
SQL Server 2012
|If you are currently running SQL 2012, you risk a preventable cyberattack. If you have taken delayed action in planning the upgrade, we recommend you move forward ASAP. Please note: resolution after an attack will be billed at time and materials for all EOL instances. SQL 2012 went EOL on 7/12/22.|
Azure AD Connect 1.X
|Azure AD Connect is an important part of your security and password syncing process. If you run Server 2016 or newer, we took care of this on your behalf. If you are on unsupported or older operating systems, like Server 2012 & 2012 R2, you’ll need to make upgrade decisions to be in compliance, and not lose functionality or face downtime.|
Azure AD Connect 1.X went EOL on 8/1/22.
Mac OS Catalina
|Using an OS that is no longer supported eliminates your ability to receive important OS service and security updates.|
We highly encourage end users to upgrade where possible or replace hardware if unsupported by Apple.
|After January 10th, 2023, devices operating on Windows 8.1 will no longer receive important service and security updates. We highly encourage end users to upgrade where possible or replace hardware if the machine is more than 4 years old.|
|After the EOL date, Microsoft will no longer be providing important service and security updates for Exchange 2013, leaving your servers vulnerable to cyberattacks. We are currently reviewing our clients utilizing Exchange 2013 and will be in touch for planning 6-9 months ahead of Exchange 2013’s retirement.|
|Microsoft will no longer send important service and security updates after EOL dates. Plan and budget for these upgrades in the last half of 2022 or in 2023.|
Windows Server 2012 & 2012 R2
|Planning for this Windows OS retirement should take place at least 6-9 months prior to the EOL date to be upgraded or migrated before October 2023.|
Please note that this does not cover everything that may affect your business, but the many common software and technologies If you would like to know more about planning for EOL, reach out to your Account Manager, Strategic Consultant or contact GadellNet at firstname.lastname@example.org.