Guides / Practice

Checklist: review your IT estate for support end dates

Support end dates usually come as a surprise because nobody has the whole estate in view. With this checklist you know within an hour which devices already run without vendor support, which are affected in the next twelve months and what to do with each.

The checklist in six steps

  • Export the inventory from your CMDB, asset management or Excel. Vendor and model are enough.
  • Paste the list into the EOSL365 inventory check. Matching runs in your browser, nothing is uploaded.
  • Split the result into three groups: already EOSL, EOSL within 12 months, active.
  • For the first two groups, decide per device: renew, replace or keep running with third-party maintenance.
  • Set an EOSL alert so no date takes you by surprise.
  • Repeat yearly, because vendors move dates.

Common pitfalls

  • Inconsistent model names (serial number instead of model, marketing name instead of type): normalise first.
  • Forgotten components: tape libraries, UPS, SAN switches and management appliances have their own support end dates.
  • Overlooked software: operating systems and hypervisors have their own dates, often before the hardware.

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 audit

Frequently asked questions

How do I find out which devices are end of support?

By matching your inventory against an EOSL database. The EOSL365 inventory check compares a pasted device list with more than 12,000 models, free and without upload.

How often should I review the estate?

At least once a year and before every renewal round. Vendors regularly move or add dates.

What do I do with devices that are already EOSL?

Decide per device: replace it if that makes sense technically, otherwise keep it running with third-party maintenance and the protective measures from the firmware guide.

→ To the EOSL database · → Software & consumer dates