OpManager: A Remote Code Execution (RCE) vulnerability could be exploited by users with 'Write' access to the 'Deploy Agent' action in the UI. This has been fixed now. (Reported by Daniel Santos. Refer: CVE-2024-5466)
General: Previously, from versions 128317 and above, Mail Servers without credentials failed to send emails and displayed an 'Authentication Unsuccessful' error. This has been fixed.
OpManager: Previously, the dropdown in the Capacity Planning Reports Rule filter was not clickable. This issue has been fixed now.
OpManager: Previously, there was an issue in saving threshold configuration for URL monitors. This has been fixed now.
OpManager: Previously, from version 128248 and above, there was an error in updating the discovery settings. This issue has been fixed.
OpManager: Previously, if OpManager was configured to use MSSQL, there were issues in sorting devices in the Inventory by 'Display Name'. This issue has been fixed now.
OpManager: Previously, from version 127257 and above, there was an issue in applying the standard edition license. This has been fixed now.
General: In builds of versions 128265 and later, the Webhook "Test Action" was not functional. This has been fixed now.
General: Previously, some mail servers didn't recognize the "NOOP" command used during communication. To fix this, an option has been provided to ignore the command for smooth communication.
Enterprise Edition: Previously, credential failure alerts were falsely raised for devices monitored using SNMPV3 credentials. This has now been fixed.
Enterprise Edition: Previously, there was startup slowness in Probes due to querying a table with a large amount of data. It has now been fixed.
Enterprise Edition: Fixed an issue related to upgrade failure and NCM Compliance policy sync during upgrade.
OpUtils: Previously, free users could add more than one switch for Switch Port Mapper in the OpManager Probe, causing users to encounter a license violation page when logging in. This has been fixed now.
Eligible Build Numbers: 128000 and above.
* - To migrate from build numbers 12.4.000 to 12.4.196 to the latest build, click here.
* -SHA256 value for the PPM: 7b49f9be21585cb26cdbbf8204a49f415009a677f0524909bb35ecd72b018661.
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 172300
Upgrade to the latest PPM with feature enhancements and recent bug fixes.
* -SHA256 value for the PPM: 1170018e11d9eff5708a38ed3f35d50637f32e252d15a10f849cce0fc74c8ec3
* - This pack can be updated directly by users with Build No. 15000 & 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 128320
Eligible Build Numbers: 128000 and above.
* - To migrate from build numbers 12.4.000 to 12.4.196 to the latest build, click here.
* -SHA256 for the PPM: 7b49f9be21585cb26cdbbf8204a49f415009a677f0524909bb35ecd72b018661.
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 128320
Eligible Build Numbers: 128000 and above.
* - To migrate from build numbers 12.4.000 to 12.4.196 to the latest build, click here.
* -SHA256 for the PPM: 7b49f9be21585cb26cdbbf8204a49f415009a677f0524909bb35ecd72b018661.
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 128320
Eligible Build Numbers: 128000 and above.
* - To migrate from build numbers 12.4.000 to 12.4.196 to the latest build, click here.
* -SHA256 for the PPM: 7b49f9be21585cb26cdbbf8204a49f415009a677f0524909bb35ecd72b018661.
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 128320
OpUtils: Previously, free users could add more than one switch for Switch Port Mapper in the OpManager Probe, causing users to encounter a license violation page when logging in. This has been fixed now.
Eligible Build Numbers: 128000 and above.
* - To migrate from build numbers 12.4.000 to 12.4.196 to the latest build, click here.
* -SHA256 for the PPM: 7b49f9be21585cb26cdbbf8204a49f415009a677f0524909bb35ecd72b018661.
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.
