Keep your Password Manager Pro deployment secure and up to date with the latest service packs and patches.
The .ppm file can be applied to the secondary Password Manager Pro server without reconfiguring high availability - as per the below-tabulated scenarios only:
| HA Architecture Type | PGSQL | MS SQL |
|---|---|---|
| Failover Service (FOS) | NA | |
| High Availability (HA) | NA | |
| Read-Only Server (RO) | NA |
Note:
Users upgrading from build 13140 to 13200 are not required to reconfigure the PGSQL High Availability.
The .ppm file can be applied to the secondary Password Manager Pro server without reconfiguring high availability - as per the below-tabulated scenarios only:
| HA Architecture Type | PGSQL | MS SQL |
|---|---|---|
| Failover Service (FOS) | NA | |
| High Availability (HA) | NA | |
| Read-Only Server (RO) | NA |
13100 Upgrade Prerequisite:
Starting from this version, Password Manager Pro no longer supports the jTDS driver. Instead, the JDBC driver will be the default driver for database connections. Users previously using jTDC as the database driver should consider the following operations for a successful upgrade:
1. Before starting the upgrade process, it is essential to complete the operation outlined here. If you have configured High Availability - MS SQL in your environment, ensure to perform the prerequisite on both the primary and secondary servers and verify that your existing High Availability setup is functioning properly before proceeding with the upgrade.
2. Upon successful primary server upgrade, perform the following operations before proceeding with the secondary server upgrade:
Execute the HAlib_13100.bat file located in the /bin folder. This will create a file named HAlib_13100.zip in the bin folder.
Copy and extract the HAlib_13100.zip file in the secondary server installation directory. i.e ManageEngine/PMP.
Upon successful extraction, proceed with the upgrade pack process on the secondary server.
The .ppm file can be applied to the secondary Password Manager Pro server without reconfiguring high availability - as per the below-tabulated scenarios only:
| HA Architecture Type | PGSQL | MS SQL |
|---|---|---|
| Failover Service (FOS) | NA | |
| High Availability (HA) | NA | |
| Read-Only Server (RO) | NA |
The .ppm file can be applied to the secondary Password Manager Pro server without reconfiguring high availability - as per the below-tabulated scenarios only:
| HA Architecture Type | PGSQL | MS SQL |
|---|---|---|
| Failover Service (FOS) | NA | |
| High Availability (HA) | NA | |
| Read-Only Server (RO) | NA |
Note:
- If you have configured HA for your Password Manager Pro instance, your primary and secondary
- If you are using Jira Service Desk as the Ticketing System, this upgrade pack will disable the
- Also, if you are using Microsoft NTLM SSO as the primary authentication method, it will no longer
Note:
- If you have configured HA for your Password Manager Pro instance, your primary and secondary
- If you are using Dropbox for cloud storage, this upgrade will delete auth tokens, and you will
Note: If you have configured HA for your Password Manager Pro instance, your primary and secondary servers should be of similar versions. For example, if you are upgrading to 12000, you should concurrently reconfigure HA and set up a fresh secondary instance that runs on 12000. Also, the software architectures of the primary and secondary servers should be the same, i.e., either both 32-bit or both 64-bit.
Note: If your current Ticketing System is ServiceDesk Plus On-Premises or ServiceDesk Plus Cloud, this upgrade pack will disable the integration and delete the complete integration data. You will have to reconfigure the ticketing system again. So, make sure you have a backup of the advanced configurations in the form of screenshots for reference purposes.
Note: Please note that the 10500 upgrade pack does not support the MySQL database.
Note: If you're using PostgreSQL as backend, note that upgrading to 9700 will remove the currently used PostgreSQL credentials from the database configuration file. Upon removing this superuser account, Password Manager Pro will automatically create another database account with minimal privileges, add the credentials to the file, and use them to launch database connections henceforth. As a precaution, it is therefore recommended to note down the current PostgreSQL credentials from the database_params.conf before upgrading since the credentials will be completely erased from the file. However, this action will not deactivate or delete the superuser database account in any way.
Note: Upgrading to 8600 will take a little longer than usual, since the upgrade pack includes PostgreSQL migration from v9.2.4 to v9.5.3
If you have Password Manager Pro configured in the secondary server(s) of your environment, refer to this section before proceeding with the upgrade pack steps given below.
<Password Manager Pro Installation Folder>/bin directory and execute UpdateManager.bat.Note: If using Windows Authentication for MS SQL, start the command prompt using the service account configured for Password Manager Pro.
/etc/init.d/pmp-service stop.<Password Manager Pro Installation Folder>/bin using the terminal.sh UpdateManager.sh -c (CLI mode).i to install and supply the full path of the downloaded .ppm file./etc/init.d/pmp-service start.