Upgrade Password Manager Pro

Upgrading PMP is fairly straightforward. The upgrade packs are applied through a tool named UpdateManager which is handily bundled within the PasswordManager Pro directory. To install the upgrade packs on an installation which doesn't have a full MS SQL Server backend just following the following steps:

1] In Windows, right-click the PMP tray icon and then click "Exit"

2] Shutdown the PasswordManager Pro Server service, if running. Check if mysql process is running. If it is, terminate that process

IMPORTANT: Take a copy of the entire Password Manager Pro installation folder before applying the upgrade pack and keep it in some other location. If something goes wrong with the PMP upgrade, you can rely on the copy. All your settings will remain intact.

3] Log onto the server as the Local Administrator (domain admin won't work for some reason). Open up an elevated cmd prompt, navigate to <PMP_Installation_Folder>/bin directory and execute UpdateManager.bat to start the Update Manager.

4] If you are applying multiple upgrade packs one-by-one, exit the Update Manager tool after applying one upgrade pack and make sure that the database process is not running. Then proceed with running the Update Manager tool to apply the next upgrade pack and so on

5] Click Browse and select .ppm file that you downloaded. Click Install to install the upgrade pack. Wait until the upgrade pack is fully installed. [Normally, it takes a few minutes for PPM installation]

6] Click Close and then click Exit to exit the Update Manager tool. If you are applying more than one upgradepack, apply them one-by-one and follow this step after applying each upgradepack 
 
7] After applying the upgrade pack, check if database process is running. If it is running, terminate that process

8] Start the PasswordManager Pro server / service

9] Once you upgrade to the latest version, the High Availability set up has to be reconfigured again. The old HA set up will not work. In addition, the existing secondary server has to be uninstalled and a new secondary server has to be installed. You may download a fresh, full build and install it as SECONDARY