OpManager is continuously enhanced and improved to deliver the best monitoring features and network security in the market. As part of this process, legacy versions of OpManager are gradually phased out, starting with an "end of support" or EOS date announcement.
After the specified EOS date, Users with legacy builds will not be able to renew their annual maintenance support (AMS) or avail technical support. Users can still continue to use OpManager at their own risk until the version's end of life (EOL) date.
There will a considerable time gap between the EOS dates and the EOL dates for a build version. This is done to minimize disruption for the users and give them time to migrate or update to newer versions. However, we strongly recommend timely updates to newer versions if a current build version is listed for end of support.
We release multiple updates every year to ensure that OpManager remains up-to-date and secure. Users who are still using very old versions of OpManager will have to perform multiple updates to upgrade to the latest version. This is a challenging endeavor that we do not recommend. With timely updates, users don't have to face such hassles and can enjoy the following advantages.
End of support denotes the dates beyond which users can't avail technical support or renew their annual maintenance and support contracts. Users can still continue to use their builds post the EOS date at their own risks. We strongly recommend prompt updates, especially since update paths from very old versions often involves multiple updates and have the risk of data loss.