Guides / Enterprise
Running servers after EOSL: risk check & practical guide
A server that has run stably for five years doesn't get worse on the EOSL cut-off date. Still, the responsibility shifts: from now on you manage the risk yourself — or with a maintenance partner. This guide shows when continued operation makes sense and how to set it up cleanly.
The risk check in four questions
- Criticality: does production/revenue depend on the system, or is it a test/dev/backup target?
- Spare-parts situation: are disks, power supplies, controllers for the platform still readily available? (For common generations: yes, for years.)
- Firmware level: is the latest available firmware installed? After EOSL there are no more patches.
- Compliance: do auditors (ISO 27001, BAIT/VAIT, NIS2) require a documented approach to unsupported infrastructure?
The practical checklist for continued operation
- Inventory: which systems are affected, which reach EOSL in the next 12-24 months? (The EOSL365 database helps.)
- Maintenance concept: third-party maintenance with SLA + spare-parts stocking for critical systems; cold-spare strategy for non-critical ones.
- Hardening: segment unsupported systems on the network, lock down management interfaces, tighten monitoring.
- Exit date: even extended operation needs a planned end — typically 2-5 years after EOSL.
What continued operation delivers economically
The business case is usually clear: instead of an early refresh (CapEx, migration project, risk), the depreciated hardware keeps running on a maintenance contract that is 30-70 % below the last vendor terms. The refresh then happens when it makes technical sense — not when the vendor's sales calendar demands it.
Partner recommendation · Ad
Have your installed base reviewed?
Our partner TechCare Solutions produces a free EOSL audit: which systems are affected, what continued operation via third-party maintenance costs, and where a refresh pays off.
Request a free EOSL auditFrequently asked questions
How long can you realistically run a server after EOSL?
Common platforms (ProLiant, PowerEdge, UCS, FAS) can typically run 3-5 years, sometimes longer, after EOSL with third-party maintenance — spare-parts supply via broker and TPM stock is usually excellent.
Is continued operation compatible with ISO 27001 / NIS2?
Yes, if it's managed: documented risk analysis, compensating measures (segmentation, monitoring), a maintenance contract with an SLA and a planned exit date. Only unmanaged sprawl is problematic.
What does third-party maintenance for a server typically cost?
Depending on platform, SLA and region — as a rule of thumb 30-60 % below the OEM maintenance price, after EOSL up to 70 % below the last OEM terms. Reputable providers price after a supportability check, not as a flat rate.