Upgrade Pack Password Manager » Features » Upgrade Pack Download

ManageEngine® Password Manager Pro Upgrade Pack Download

The latest PMP version is 8.5 (8504). If you are using an earlier version, you need to apply upgradepack. How do I find my build number?

Download Upgrade Pack | Upgradepack Instructions

From 8500/8501/8502/8503 to 8504 Upgrade pack 8500/8501/8502/8503 to 8504
From 8400/8401/8402/8403/8404 to 8500 Upgrade pack 8400/8401/8402/8403/8404 to 8500
From 8300/8301/8302/8303 to 8400 Upgrade pack 8300/8301/8302/8303 to 8400
From 8200 to 8300 Upgrade pack 8200 to 8300
From 8100/8101/8102 to 8200 Upgrade pack 8100/8101/8102 to 8200
From 8000/8001 to 8100 Upgrade pack 8000/8001 to 8100
From 7600 to 8000 Upgrade pack 7600 to 8000
From 7500/7501 to 7600 Upgrade pack 7500/7501 to 7600
From 7100/7101/7102/7103/7104/7105 to 7500 Upgrade pack 7100/7101/7102/7103/7104/7105 to 7500
From 7000/7001/7002/7003 to 7100 Upgrade pack 7000/7001/7002/7003 to 7100
Before applying this upgradepack, follow these instructions.
From 6900/6901/6902/6903/6904 to 7000 Upgrade pack 6900/ 6901/ 6902/ 6903/ 6904 to 7000
From 6800/6801/6802/6803 to 6900 Upgrade pack 6800/6801/6802/6803 to 6900
From 6700/6701/6800/6801 to 6802 Upgrade pack 6700/6701/6800/6801 to 6802
From 6600 to 6700 Upgrade pack 6600 to 6700
From 6500/6501/6502/6503/6504/6505 to 6600 Upgrade pack 6500/6501/6502/6503/6504/6505 to 6600
From 6404 to 6500 Upgrade pack 6404 to 6500
From 6400/6401/6402/6403 to 6404 Upgrade pack 6400/6401/6402/6403 to 6404
From 6303 and earlier versions Contact Support

Instructions to apply the Upgrade Pack
Windows (MySQL / PostgreSQL) | Windows (MS SQL) | Linux

Windows (MySQL / PostgrerSQL)

  • Stop Password Manager Pro service and exit the tray icon.
  • Shut down Password Manager Pro service - both primary and secondary, if running. Also, make sure that postgres / mysql process is not running in task manager.
  • Note:

    1. If you are using versions 8500 and above, the following steps can be applied to both primary as well as the secondary setups configured for high availability. Execute the steps first for the primary service and then for the secondary, respectively.
    2. For versions older than 8500, the secondary server should be completely uninstalled and high availability has to be reconfigured after the upgrade. To set up a fresh secondary instance of Password Manager Pro, follow the steps given here.
  • Take a backup of the entire Password Manager Pro installation folder and store it in some other location. If something goes wrong with the upgrade, you can revert back to this copy, with your settings intact. If you are using versions 8300 and above, you need to follow these instructions before applying the upgrade packs.
  • Now, right click on command prompt and run as administrator.
  • Navigate to <PMP_Installation_Folder>/bin directory from CMD and execute UpdateManager.bat
  • Click Browse and select the .ppm file that you downloaded. Then, Install.
  • In case of multiple upgrade packs, exit Update Manager after applying each upgrade pack and ensure the database process is not running. Then, reopen Update Manager to apply the next upgrade pack.
  • After applying the upgrade packs, start the Password Manager Pro service.

If you need any assistance or clarifications, please contact passwordmanagerpro-support@manageengine.com.

Windows (MS SQL)

Prerequisite

  • Stop Password Manager Pro service and exit the tray icon.
  • Shut down Password Manager Pro service - both primary and secondary, if running. Also, make sure that postgres / mysql process is not running in task manager.
  • Note:

    1. If you are using versions 8500 and above, the following steps can be applied to both primary as well as the secondary setups configured for high availability. Execute the steps first for the primary service and then for the secondary, respectively.
    2. For versions older than 8500, the secondary server should be completely uninstalled and high availability has to be reconfigured after the upgrade. To set up a fresh secondary instance of Password Manager Pro, follow the steps given here.
  • Take a backup of the entire Password Manager Pro installation folder and store it in some other location. If something goes wrong with the upgrade, you can revert back to this copy, with your settings intact. Additionally, take a backup of the Password Manager Pro database. If you are using versions 8300 and above, you need to follow these instructions before applying the upgrade packs.

Applying Upgradepack

  • Navigate to <PMP_Installation_Folder>/bin directory from CMD and execute UpdateManager.bat
  • 1. During MS SQL server configuration for Password Manager Pro database, if you have opted for 'Windows Authentication,' you have to start the command prompt using the service account with which the Password Manager Pro service has been configured to connect to the SQL server (i.e. instead of running as administrator, run as the service account).

    2.To identify whether a service account is used or an SQL account is used, navigate to <PMP_Installation_Folder>/conf directory and open database_params.conf file. If you do not find a username and password in the file, then Password Manager Pro is using Windows Authentication and therefore you need to run the command prompt with service account privilege.

  • Click Browse and select the .ppm file that you downloaded. Then, Install.
  • In case of multiple upgrade packs, exit Update Manager after applying each upgrade pack and ensure the database process is not running. Then, reopen Update Manager to apply the next upgrade pack.
  • After applying the upgrade packs, start the Password Manager Pro service.

Linux (Headless)

  • Stop Password Manager Pro service using the command /etc/init.d/pmp-service stop.
  • Shut down Password Manager Pro service - both primary and secondary, if running. Also, make sure that postgres / mysql process is not running in task manager.
  • Note:

    1. If you are using versions 8500 and above, the following steps can be applied to both primary as well as the secondary setups configured for high availability. Execute the steps first for the primary service and then for the secondary, respectively.
    2. For versions older than 8500, the secondary server should be completely uninstalled and high availability has to be reconfigured after the upgrade. To set up a fresh secondary instance of Password Manager Pro, follow the steps given here.
  • Take a backup of the entire Password Manager Pro installation folder and store it in some other location. If something goes wrong with the upgrade, you can revert back to this copy, with your settings intact. If you are using versions 8300 and above, you need to follow these instructions before applying the upgrade packs.
  • Navigate to <PMP_Installation_Folder>/bin directory using terminal.
  • Execute the command sh UpdateManager.sh -c (This will run the Update Manager in CLI mode)
  • Now, press i to install. Supply full path of the upgrade pack and wait for the upgrade to complete until the message "Service Pack applied successfully" is displayed.
  • In case of multiple upgrade packs, exit Update Manager after applying each upgrade pack and ensure the database process is not running. Then, reopen Update Manager to apply the next upgrade pack.
  • After applying the upgrade packs, start the Password Manager Pro service, using /etc/init.d/pmp-service start

If you need any assistance or clarifications, please contact
passwordmanagerpro-support@manageengine.com.


Instructions to upgrade Password Manager Pro (Steps applicable when upgrading from builds 8300 and later)

The latest version of PMP enforces a security best practice. So, before proceeding with this upgrade, you need to read the instructions below carefully.These steps are applicable only when upgrading from builds 8300 and later.

1. As a security precaution, Password Manager Pro will not allow using the username itself as the password anymore. System default admin and guest users who are using the username itself as the password need to reset the passwords of those default accounts before proceeding with the upgrade pack installation process.

2. System default admin and guest users should use the 'Change Login Password' wizard to reset their local authentication password.

Role- specific steps to change local authentication password:

Administrator and Password Administrator Navigate to Admin » 'Change Password' in the 'General' tab -> set a new password.
Password Auditor and Password User Click the user account icon on the top right corner of the PMP web-interface » 'Change Password' » set a new password.

3. The new password should be compliant with the password policy assigned by your administrator. You can take the help of the password generator to generate new password or type new password yourself as per the policy.

4. Make sure to remember your new password as it will NOT be emailed. If you forgot your password, use the 'Forgot password' link available on the login page of PMP to reset your password.

5. After the upgrade process, PMP will also force all users to reset their local authentication password whose username and password are the same.


Instructions to upgrade to JRE 7 (Steps applicable when upgrading from builds 7000 and later)

Latest version of PMP runs with JRE v7u51. So, before proceeding with this upgrade, you need to download JRE and follow the instructions below. These steps are applicable only when upgrading from builds 7000 and later.

If you have installed PMP in Windows

  1. Ensure that PMP server is not running. In case, PMP is running as a service, shutdown that too. Also, check if mysql / postgres process is running. If so, terminate that process.
  2. Navigate to <PMP Installation directory>. You will see a folder named jre. Rename it as jre6
  3. Download the jre_windows_7u51.zip, copy the zip and paste it directly under <PMP Installation directory>
  4. Unzip the jre_windows_7u51.zip. This will create a folder named jre under <PMP installation directory>
  5. Now, navigate to the old jre6 (the one you renamed in step 2) available under <PMP-Installation-Directory>/jre6/lib/security/ folder. You will find a file named cacerts. Copy that file.
  6. Now, navigate to the new jre available under <PMP-Installation-Directory>/jre/lib/security/ and paste the cacerts you copied in the previous step.
  7. Now, run UpdateManager.bat and proceed with the upgrade

If you have installed PMP in Linux

  1. Ensure that PMP server is not running. Also, check if mysql / postgres process is running. If so, terminate that process.
  2. Navigate to <PMP Installation directory>. You will see a folder named jre. Rename it as jre6
  3. Download the jre_linux_7u51.zip, copy the zip and paste it directly under <PMP Installation directory>
  4. Unzip the jre_linux_7u51.zip. This will create a folder named jre under <PMP installation directory>
  5. Now, navigate to the old jre6 (the one you renamed in step 2) available under <PMP-Installation-Directory>/jre6/lib/security/ folder. You will find a file named cacerts. Copy that file.
  6. Now, navigate to the new jre available under <PMP-Installation-Directory>/jre/lib/security/ and paste the cacerts you copied in the previous step.
  7. Now, run UpdateManager.sh and proceed with the upgrade

How do I find out my Build number?

Log in to the PasswordManager Pro web interface, and click the About link in the top pane. You will find the build number mentioned below the version number. This is the build number of the currently installed PasswordManager Pro.

Password Manager Pro - Enterprise Password Management Software trusted by