General: Previously, upgrades from base version 12.8.586 or higher were blocked at the precheck phase due to a scheduler-initiated Database Analyzer operation in certain scenarios. This issue has now been fixed.
General: Previously, a DOM-based XSS vulnerability was identified due to improper handling of message data in HTML. This issue has now been fixed. (Reported by Daniel Santos)
Enterprise Edition: Previously, when manual thresholds were set in Central, adaptive thresholds for CPU and Memory monitors were still retained on newly installed Probes. This has been fixed now.
OpManager: Previously, a Command Line Injection vulnerability was detected in the Notification Profiles module. This has now been fixed. (Reported by Daniel Santos)
OpManager: Previously, while associating Custom SNMP monitors, there was an issue where the display names were not mapped correctly if the DNS was not resolved. This has been fixed now.
OpManager: Previously, there was an issue fetching the MAC Address for a few SNMP devices on the Device Summary page. This issue has now been fixed.
OpManager: Previously, in IPMI device snapshot page, there was a redirection issue in the Managing servers widget. This has been fixed now.
OpManager: Previously, EventLog Monitors associated to unmanaged devices initiated polling when the server restarted. This has been fixed now.
OpManager: Previously, when the OpManager UI was accessed from a device in a different time zone, performance monitor graphs displayed incorrect values for custom time periods. This has been fixed now.
OpManager: Previously, there was a rare issue where the SNMPv3 handshake failed to initialize, causing data collection failures in firewall devices. This has been fixed now.
OpManager: Previously, false SNMPv3 alerts generated by the Data Collection Manager due to excessive SNMP requests. This has been fixed now.
OpManager: Previously, there were Intermittent data collection failures caused by SNMPv3 cache errors. This has been fixed now.
OpManager: An option has been introduced to automatically update interface indexes during data collection when changes are detected in the environment.
OpManager: Previously, IP address changes made in a probe did not sync to Central if another probe had assigned the same IP to a device. This issue has now been fixed.
OpManager: Previously, applying a Device Template would dissociate the Performance Monitor linked to the custom field 'Serial Number'. This issue has now been fixed.
OpManager: Previously, Rx/Tx traffic data was not collected for Palo Alto VPN tunnels. This issue has now been fixed.
OpManager: previously, there was a discrepancy between the 'VPN Tunnels Down' widget and the VPN tab data in the device snapshot. This has now been fixed.
OpManager: Previously, stale entries were added due to an internal issue in the scheduled interface discovery process. This has been fixed now.
OpManager: Previously, rediscovering a device without interfaces would delete packet loss and response time statistics. This issue has now been fixed.
OpManager: Previously, adding a Huawei AC 6508 controller triggered a "WLC model mismatch" error. This issue has now been fixed.
OpManager: Previously, WLC discovery could fetch the wrong model because of improper SysOID evaluation when a default device template was missing. This issue has now been fixed.
OpManager: Previously, tooltips did not appear on the Google Map page when multiple devices were located at the same coordinates. This issue has now been fixed.
OpManager: Previously, when importing custom fields via CSV, some column values were not updated for certain devices due to an internal issue. This has now been fixed.
OpManager: Previously, the device down reason wasn't visible in the down event once the device is Up. This issue has now been fixed.
OpManager: Around 300 device templates have been added for a wider support of device models during device discovery.
OpManager: Some devices in OpManager failed to sync to ServiceDesk Plus On-Premise when the total number of devices exceeded 1,000. This issue has now been fixed.
OpManager: Previously, there was an issue syncing devices to ServiceDesk Plus MSP under categories that contained spaces in their names. This has now been fixed.
OpManager: Previously, when ServiceDesk Plus On-Premise was integrated with OpManager there was an issue with syncing the child citype devices under Servers or Workstations. This has now been fixed.
OpManager: Previously, when ServiceDesk Plus On-Premise was integrated with OpManager, there was an issue where the OS versions were failed to sync. This has now been fixed.
OpManager: Previously, in certain cases, Out of Memory issue occurred when ServiceNow was configured in OpManager. This issue has now been fixed.
OpManager: Previously, from version 128582, there was an issue with alarm notes overlapping text in alarms list page. This has now been fixed.
OpManager: Previously, slowness was observed while accessing the Inventory tab, due to an issue while fetching the applications count. This has now been fixed.
OpManager: Previously, from version 128540, the suppression data was fetched in the listDevices and listInterfaces APIs even when the ‘suppressed’ column was not selected in the column chooser under Inventory page. This has now been fixed
OpManager: Previously, Windows Service Down alerts were triggered incorrectly when WMI query execution failed for Windows Agent–monitored devices. This issue has now been resolved.
OpManager: Previously, the Windows Agent stopped working during Interface data collection when 64-bit–based data was received. This issue has now been fixed.
OpManager: Previously, from Version 128455, the listDevices API encountered latency when Custom Fields from OpUtils was enabled in Column Chooser. This issue is now fixed.
OpManager: In addition to devices, WANIP and WANIP Site monitors can now be selected as parent dependencies for uplink status calculation.
OpManager: You can now configure uplink dependencies using device groups, allowing for bulk management and simplified monitoring rules.
OpManager: A new global configuration is available to trigger an alarm only after a WANIP monitor is down for a user-defined number of consecutive checks, reducing false positives.
OpManager: Previously, in Report Builder interface graphs, consolidated table values were displayed in bytes instead of properly formatted speed units. This has been fixed now.
OpManager: Previously, the Storage Growth Trend report could not be generated due to missing data points. This has been fixed now.
OpManager: Previously, an error occurred while viewing or generating scheduled advanced reports in Azure DB instances. This has been fixed now.
OpManager: OpManager now integrates with OpenAI to deliver contextual summaries for alerts, device and device group details, as well as generate scripts based on natural language inputs.
OpManager: Previously, expanding the Traffic widget under WAN IP Snapshot > Traffic showed no data in the Summary table. This issue has now been fixed.
OpManager: Previously, the Availability dial in snapshot pages did not display data for longer time period. This issue has now been resolved.
OpManager Storage Monitoring: Previously, there were discrepancies in the performance monitor data for Dell Compellent and PowerStore storage devices. This has been fixed now.
OpManager Storage Monitoring: Previously, host and volume mappings for PowerStore devices were not updated correctly. This has been fixed now.
OpManager Storage Monitoring: Previously, the disk count for EqualLogic devices was displayed incorrectly. This has been fixed now.
OpManager Storage Monitoring: Previously, there was an issue during the discovery of NetApp E-Series storage devices. This has been fixed now.
OpManager Storage Monitoring: Previously, there was an issue with SNMPv3 credentials during status polling of Synology DSM storage devices. This has been fixed now.
OpManager Storage Monitoring: Previously, the disk online status of NetApp ONTAP storage devices was displayed incorrectly. This has been fixed now.
OpManager: XSS vulnerability detected in the Heatmap widget upon enabling 'Show label', has been fixed now. (Reported by Daniel Santos).
OpManager: Special characters in device or interface display names are automatically sanitized and replaced with a hyphen (-) to prevent vulnerability issues.
OpManager: From version 128610, the following alarm widgets did not list interface alarms when a device group containing interface alarms was selected in the filter. This issue has now been fixed: All Alarms, Recent Alarms, Unacknowledged Alarms, Recent Events, and Web Alarms.
OpUtils: Previously, users with read only or operator access were able to delete Tool SNMP traps. This issue has now been fixed. Refer : ZVE-2025-5566
OpUtils: Previously, there was an issue that prevented modifying the Tools SNMP traps port via settings. This issue has now been fixed.
OpUtils: Previously, there was an issue with updating the router CLI credentials. This issue has been fixed now.
NCM: ComplianceIQ now supports creating flow rules using XPath for compliance checks on XML-based device configurations.
NCM: New CIS standard policies are now supported, including CIS Cisco NX-OS v1.2.0, CIS Palo Alto Firewall 11 v1.2.0, and CIS Juniper OS v2.1.0.
NCM: Compliance report exports in CSV and XLS formats now include additional columns for Violation Message and Violation Severity.
NCM: Introduced an option in the client-server settings to disable the Compliance Check during configuration backup, if required.
NCM: Previously, exporting compliance reports to CSV and XLS formats failed due to an internal issue. This has now been fixed.
NCM: Previously, when selecting a device or device group while adding or updating a schedule, or during configlet execution, an error was thrown if the selected language was other than English. This issue has now been fixed.
NetFlow: SmartUpgrade and Emergency Patch capabilities are now supported in the NetFlow Analyzer Enterprise Edition.
Eligible Build Numbers: 12.8.000 and above.
* - To migrate from build numbers 12.4.000 to 12.4.196 to the latest build, click here.
* -SHA256 for the PPM: 1e9a2d642b7873f37cce6a4bf08ae685e0f56eabbf1be707ad04d6ed61110698
Read and accept the License Agreement before downloading this software.
Steps to upgrade Service Pack:
I. For builds 12.8.000 and above
Shut down OpManager/NetFlow Analyzer/Network Configuration Manager/Firewall Analyzer/OpUtils. (If the application is running as a Windows service, stop the service from Control Panel > Services window and close the window.)
Start the Command Prompt as an administrator: Search for “cmd”, right-click Command Prompt, then select Run as administrator.
End the processes: Open the Task Manager and make sure the processes java.exe or wrapper.exe of the application are terminated.
Backup the application folder. Make a copy of the '<OpManager-home-directory>' folder. This will back up the product configuration settings.
Launch Update Manager:
Windows OS: Go to the <OpManager-home-directory>/bin folder and run the script UpdateManager.bat
Linux OS: Go to the <OpManager-home-directory>/bin folder and run the script UpdateManager.sh
Click the Browse button to select the upgrade pack file (the .ppm file that you downloaded) and choose Install.
Follow the on-screen instructions to apply the service pack
Once the upgrade is complete, start the service for the changes to take effect.
Note: Applications Manager plugin, if present, should be upgraded to version 14540 or above before upgrading OpManager from version 12.5 to 12.5.100 and higher versions.
Back up your DB and VM snapshot folder before initiating the upgrade.
Antivirus has to be disabled until the upgrade is complete.
All files and folders under the <OpManagerHome>/pgsql directory should be closed before initiating the upgrade.
No file under the <OpManagerHome>/pgsql directory should be opened during the upgrade process.
The free disk space should be greater than 1.25x the size of the <OpManagerHome>/pgsql/data folder.
Step 2: Upgrade to build 12.5.383
** Points to note:
You will not be able to upgrade from build 12.5.011 to 12.5.383 if the historical migration is not complete.
The migration details can be checked under Settings > General Settings > Migration Status.
Applications Manager plugin, if present, should be upgraded to version 14540 or above before upgrading OpManager from version 12.5 to 12.5.100 and higher versions.
Applications Manager Build Number 178204
Upgrade to the latest PPM with feature enhancements and recent bug fixes.
* -SHA256 for the PPM: 7f444cb122dd13992556701d9322388dfd9c11500d46d46925f008b62b8c9d13
* - This pack can be updated directly by users with Build No. 170000 & above. * - For older versions, visit this page.
Read and accept the License Agreement before downloading this software.
Steps to update service pack:
Shut down Applications Manager as you normally do.
Via command prompt, execute the shutdownApplicationsManager.bat -force command (shutdownApplicationsManager.sh -force for Linux) from the 'Applications Manager Home' folder.
As a best practice, take complete backup of 'Applications Manager Home' directory. SQL backend users should connect to SQL Management Studio & backup the AMDB database as well. click here. to know how to backup SQL database.
Run the updateManager.bat script (updateManager.sh -c for Linux) under the 'Applications Manager Home/bin' folder which invokes the Update Manager tool.
Browse and select the Service pack file (.ppm) saved in your computer.
You might be asked to import the ManageEngine public key certificate (ppmsigner_publickey.crt) file during the upgrade process. If asked, download the certificate file, then browse and select the downloaded file to proceed further.
Note: This is a one-time process done to verify the integrity of the service pack (.ppm) file.
Click Install to initiate the upgrade process.
Once you see the "Installed" message on your screen, click Finish to complete the installation.
Start Applications Manager Server.
Note: To rollback to the old version, rename the existing 'Applications Manager Home' directory and restore the complete backup copy of this directory. SQL backend users should connect to SQL Management Studio & restore the AMDB database backup as well. Click here to know how to restore the SQL database backup.
NetFlow Analyzer - Build Number 12.8.665
Eligible Build Numbers: 12.8.000 and above.
* - To migrate from build numbers 12.4.000 to 12.4.196 to the latest build, click here.
* -SHA256 for the PPM: 1e9a2d642b7873f37cce6a4bf08ae685e0f56eabbf1be707ad04d6ed61110698
Read and accept the License Agreement before downloading this software.
Steps to upgrade Service Pack:
I. For builds 12.8.000 and above
Shut down OpManager/NetFlow Analyzer/Network Configuration Manager/Firewall Analyzer/OpUtils. (If the application is running as a Windows service, stop the service from Control Panel > Services window and close the window.)
Start the Command Prompt as an administrator: Search for “cmd”, right-click Command Prompt, then select Run as administrator.
Back up your DB and VM snapshot folder before initiating the upgrade.
Antivirus has to be disabled until the upgrade is complete.
All files and folders under the <OpManagerHome>/pgsql directory should be closed before initiating the upgrade.
No file under the <OpManagerHome>/pgsql directory should be opened during the upgrade process.
The free disk space should be greater than 1.25x the size of the <OpManagerHome>/pgsql/data folder.
Step 2: Upgrade to build 12.5.383
** Points to note:
You will not be able to upgrade from build 12.5.011 to 12.5.383 if the historical migration is not complete.
The migration details can be checked under Settings > General Settings > Migration Status.
Network Configuration Manager - Build Number 12.8.665
Eligible Build Numbers: 12.8.000 and above.
* - To migrate from build numbers 12.4.000 to 12.4.196 to the latest build, click here.
* -SHA256 for the PPM: 1e9a2d642b7873f37cce6a4bf08ae685e0f56eabbf1be707ad04d6ed61110698
Read and accept the License Agreement before downloading this software.
Steps to upgrade Service Pack:
I. For builds 12.8.000 and above
Shut down OpManager/NetFlow Analyzer/Network Configuration Manager/Firewall Analyzer/OpUtils. (If the application is running as a Windows service, stop the service from Control Panel > Services window and close the window.)
Start the Command Prompt as an administrator: Search for “cmd”, right-click Command Prompt, then select Run as administrator.
Back up your DB and VM snapshot folder before initiating the upgrade.
Antivirus has to be disabled until the upgrade is complete.
All files and folders under the <OpManagerHome>/pgsql directory should be closed before initiating the upgrade.
No file under the <OpManagerHome>/pgsql directory should be opened during the upgrade process.
The free disk space should be greater than 1.25x the size of the <OpManagerHome>/pgsql/data folder.
Step 2: Upgrade to build 12.5.383
** Points to note:
You will not be able to upgrade from build 12.5.011 to 12.5.383 if the historical migration is not complete.
The migration details can be checked under Settings > General Settings > Migration Status.
Firewall Analyzer - Build Number 12.8.665
Eligible Build Numbers: 12.8.000 and above.
* - To migrate from build numbers 12.4.000 to 12.4.196 to the latest build, click here.
* -SHA256 for the PPM: 1e9a2d642b7873f37cce6a4bf08ae685e0f56eabbf1be707ad04d6ed61110698
Read and accept the License Agreement before downloading this software.
Steps to upgrade Service Pack:
I. For builds 12.8.000 and above
Shut down OpManager/NetFlow Analyzer/Network Configuration Manager/Firewall Analyzer/OpUtils. (If the application is running as a Windows service, stop the service from Control Panel > Services window and close the window.)
Start the Command Prompt as an administrator: Search for “cmd”, right-click Command Prompt, then select Run as administrator.
Back up your DB and VM snapshot folder before initiating the upgrade.
Antivirus has to be disabled until the upgrade is complete.
All files and folders under the <OpManagerHome>/pgsql directory should be closed before initiating the upgrade.
No file under the <OpManagerHome>/pgsql directory should be opened during the upgrade process.
The free disk space should be greater than 1.25x the size of the <OpManagerHome>/pgsql/data folder.
Step 2: Upgrade to build 12.5.383
** Points to note:
You will not be able to upgrade from build 12.5.011 to 12.5.383 if the historical migration is not complete.
The migration details can be checked under Settings > General Settings > Migration Status.
OpUtils - Build Number 12.8.665
Eligible Build Numbers: 12.8.000 and above.
* - To migrate from build numbers 12.4.000 to 12.4.196 to the latest build, click here.
* -SHA256 for the PPM: 1e9a2d642b7873f37cce6a4bf08ae685e0f56eabbf1be707ad04d6ed61110698
Read and accept the License Agreement before downloading this software.
Steps to upgrade Service Pack:
I. For builds 12.8.000 and above
Shut down OpManager/NetFlow Analyzer/Network Configuration Manager/Firewall Analyzer/OpUtils. (If the application is running as a Windows service, stop the service from Control Panel > Services window and close the window.)
Start the Command Prompt as an administrator: Search for “cmd”, right-click Command Prompt, then select Run as administrator.
