OpManager Upgrade packs

Service Pack for 125000 & above customers

We strongly recommend you to take backups before updating. This helps you prevent accidental loss of data.

Version 125182

(Released on September 18, 2020)

Read and accept the License Agreement before downloading this software.

Upgrade path for previous versions | Steps to apply service pack | README | Find my build number

How to apply service pack?

1. Choose your
upgrade path.
2. Download the
appropriate PPM file.
3. Apply it in
OpManager.
4. Restart
OpManager.

Choose your upgrade path

Current build	Upgrade path to the latest build
125007 & above	Install the service pack to move to the latest build.
124006 to 124196	Install the service pack to move to the build 125007
123000 to 123329	Install the service pack to move to the build 124006
12200	Fill this form to migrate to build 123000
12000 / 12100	Install the Service Pack to move to build 12200
11600	Fill this form to download the service pack to move to build 12200 ( Watch video )

Note:

End of support has been announced for all OpManager versions till 11.6
Only users with a valid AMS (Annual Maintenance and Support) contract are eligible to download Service packs and other upgrades. Refer https://www.manageengine.com/support.html for more details.
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.

Steps to apply the service pack to OpManager

Standard/Professional Edition
1. Shut down OpManager. (If OpManager is running as a Windows service, stop the service from Control Panel > Services window and close the window.)
2. Start the Command Prompt as an administrator: Search for “cmd”, right-click Command Prompt, then select Run as administrator. (Click here to see the screenshot)
3. Back up the database (follow the steps here).
4. End the processes: Open the Task Manager and make sure the processes java.exe or wrapper.exe of the application are terminated.
5. Back up the application folder: Make a copy of the folder. This will back up the product configuration settings.
6. Launch Update Manager:
  - Windows OS: Go to the /bin folder and run the script UpdateManager.bat
  - Linux OS: Go to the /bin folder and run the script UpdateManager.sh
7. Click the Browse button to select the upgrade pack file (the .ppm file that you downloaded) and choose Install.
8. Follow the on-screen instructions to apply the service pack.
9. Once the upgrade is complete, start the service for the changes to take effect.
Enterprise Edition
Step 1: OpManager Database Backup
1. Stop the OpManager Central and all probe services.
2. Backup the OpManager database in one of the following methods:
  1. If the backend database is installed on an MSSQL server, take an SQL backup of OpManager database and all the dependent plug-in databases.
  2. If OpManager is installed on a Windows machine, go to the bin > backup folder under OpManager installation directory and execute the BackupDB.bat as administrator for the Central server and all probe servers.
  3. If OpManager is installed on a Linux machine, go to the bin > backup folder under OpManager installation directory and execute the BackupDB.sh as root user for the Central server and all probe servers.
  4. If OpManager is installed on a virtual machine, take a VM snapshot of the Central and all probes.
Step 2: updating the Central Server
1. Start all Probe services for Smart Update to take effect.
2. Go to the bin folder under OpManagerCentral installation directory.
  1. Windows OS: Run the UpdateManager.bat file as administrator.
  2. Linux OS: Run the UpdateManager.sh file as root user.
3. The Update Manager launcher appears on the screen.
4. Browse the required Update Pack file and click on Install.
5. Follow the on-screen instructions to apply the Update Pack.
6. Once the update is complete, start the OpManagerCentral Service for the update to take effect.
Step 3: Smart Update (Automatic updating of Probe servers)
1. The Probe will automatically contact the Central server.
2. Once the Probe server detects a build number mismatch with the Central server, all the Probe services will be stopped.
3. The Probe server downloads the Update Pack from the Central server and starts updating.
4. Once the update process is complete, restart all Probe services.

Remember, if you are applying more than one update pack, you have to follow the instructions above for each update pack. For instance, if you are on build 124196 and have to move to 125129, here's how you should go about it:

Follow the steps (coressponding to your OpManager Edition) to update to build 125005.
Ensure you start OpManager after this update.
Again stop OpManager and follow the update steps (coressponding to your OpManager Edition) to move to build 125129.

How can I find the build number of OpManager?

In the Web Client, click on the "Administrator" icon in the top right corner of the page.
Search for the 'Build Number' among the product details listed.
Check the following image guide to locate the build number.

Need help ?

Want help with upgrading OpManager to the latest version? Contact OpManager Support.

Know what's coming up next with OpManager. Head to our product roadmap page.

Video Zone

Altaleb Alshenqiti - Ministry of National Guard - Health Affairs

IT Admin from "Royal flying doctor service", Australia

Jonathan ManageEngine Customer
Michael - Network & Tech, ManageEngine Customer

Altaleb Alshenqiti - Ministry of National Guard - Health Affairs
David Tremont, Associate Directory of Infrastructure,USA

Todd Haverstock Administrative Director
Donald Stewart, IT Manager from Crest Industries

John Rosser, MIS Manager - Yale Chase Equipment & Services