Sweating of assets—or getting the most value of assets already owned—has been identified as one of the most common causes of network issues. Network admins often continue to use their network devices even after those devices have been branded obsolete or unsupported by the vendor. This can lead to disasters resulting from vulnerabilities or hardware failure, which is why keeping track of the end of support, end of sale, and end of life—EOL/EOS for short—information of the devices on your network is extremely important. But when your network consists of numerous devices, maintaining records of the EOL/EOS information of each device on your network can be difficult. Before we discuss Network Configuration Manager's EOL/EOS reports in detail, let's look into what these terms mean and how ignoring them can disrupt your network's function.
For EOL/EOS sync, we get data from Network Configuration Manager's ManageEngine database: https://ncm.nimbuspop.com. Customers must allow this domain in order to get those data.
End of support (EOS) |
End of sale (EOS) |
End of life (EOL) |
|---|---|---|
|
|
|
The Sync EOL/EOS feature enables administrators to update device lifecycle information by retrieving the latest End-of-Life (EOL) and End-of-Support (EOS) data from the vendor database. Keeping this information current ensures accurate reporting, helps identify obsolete or unsupported devices, and supports informed decisions for hardware refresh and risk mitigation.
In highly secure or closed environments, external internet access is restricted by design. For such networks, syncing EOL/EOS data directly from ManageEngine's cloud-based database (https://ncm.nimbuspop.com) may not be an option. This presents a challenge when administrators need to keep track of outdated or unsupported devices without violating network isolation policies.
To solve this, we’ve introduced EOL/EOS offline sync in build 128457 of Network Configuration Manager.
This new feature enables admins to update EOL/EOS data manually, without requiring a live connection to the external database. It ensures that even internet-restricted environments remain secure and up to date with the latest device lifecycle information.
Sometimes EOL/EOS dates are not available by default, forcing an admin to manually search for them or contact the vendor. However, doing so would be rather difficult when an admin needs EOL/EOS information for many devices. Network Configuration Manager makes this simpler for admins with the option to request an EOL/EOS database update. This option will send a list of the SysOIDs and other device details to our support team, which will then be used to populate the database with corresponding EOL/EOS network device data.
The primary objective of EOL/EOS reports is to ensure that there's no loss of productivity due to unsupported or obsolete hardware. The reports do this by informing admins on decisions like purchasing extended support and decommissioning devices to avoid any chances of performance degradation, data breaches, or network outages. They also aid in auditing and allocating funds for both purchasing extended support and replacement devices. Also, EOL / EOS report can be generated in both PDF and CSV formats. And EOL announced column will not be available in PDF format.