Get Quote Free Trial
System Update Center

ManageEngine PAM360 Service Packs

Keep your PAM360 deployment secure and up to date with the latest service packs and patches.

View Downloads
Server Update Process

Available PAM360 Upgrade Packs

From 8400 to 8500

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 8300 to 8400

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 8200 to 8300

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 8100 to 8200

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 8000 to 8100

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 7500 to 8000

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 7400 to 7500

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 7300 to 7400

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 7200 to 7300

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 7100 to 7200

Upgrade Pack

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 7000 to 7100

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 6700 to 7000

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 6600 to 6700

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

Note: Users who have downloaded the PAM360 build 6600 are strongly advised to use the latest 6601 build and SHA256 checksum hash value to ensure security measures and mitigate the risk of unauthorized access.

From 6500 to 6600

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

Note: Users who have downloaded the PAM360 build 6600 are strongly advised to use the latest 6601 build and SHA256 checksum hash value to ensure security measures and mitigate the risk of unauthorized access.

From 6400 to 6500

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 6300 to 6400

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

Note: For customers utilizing LDAP authentication in their environment and MS SQL as the backend database, please ensure to reconfigure the High Availability post the primary server upgrade. However, for customers not using LDAP, the upgrade pack will work seamlessly on both primary and secondary servers without requiring High Availability reconfiguration post upgrade.

From 6200 to 6300

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 6100 to 6200

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 6000 to 6100

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 5950 to 6000

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 5900 to 5950

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 5800 to 5900

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 5700 to 5800

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 5600 to 5700

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 5500 to 5600

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

Note: If you are using Dropbox for cloud storage, this upgrade will delete auth tokens, and you will have to reconfigure PAM360 storage in Dropbox.

From 5400 to 5500

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

Note: If you are using Dropbox for cloud storage, this upgrade will delete auth tokens, and you will have to reconfigure PAM360 storage in Dropbox.

From 5300 to 5400

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 5200 to 5300

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

From 5100 to 5200

Upgrade Pack Direct Installation

The .ppm file can be applied to the secondary PAM360 server without reconfiguring high availability - as per the below-tabulated scenarios only:

HA Architecture Type PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO) NA

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.

From 5000 / 5001 / 5002 / 5003 / 5004 to 5100

Upgrade Pack Direct Installation

From 4500 / 4501 to 5000

Upgrade Pack Direct Installation

From 4100 / 4101 to 4500

Upgrade Pack Direct Installation

From 4000 / 4001 / 4002 to 4100

Upgrade Pack Direct Installation

Note: Kindly upgrade to the latest version to setup HA.

Upgrade Pack Instructions based on Operating Systems

If you have PAM360 configured in the secondary server(s) of your environment, refer to this section before proceeding with the upgrade pack steps given below.

1. Windows

Prerequisites
  • Stop the PAM360 service and exit the tray icon.
    Note: If you store the 'database_params.conf' file in a different location, copy the file back to the original location, i.e., '<PAM360 Installation Folder>/conf/', before performing the upgrade.
  • Shutdown the PAM360 service - both primary and secondary, if running (Not applicable for Read-Only servers).
    Notes: If using PostgreSQL, ensure the Postgres process is not running. If using MSSQL, ensure the OpenJDK/Zulu platform process is not running.
  • Perform a backup of the entire PAM360 installation folder, and take a backup of the PAM360 database.
Steps Required
  1. Run the Command Prompt as administrator.
  2. Navigate to the <PAM360_Installation_Folder>/bin directory and execute UpdateManager.bat.
  3. Click Browse and select the .ppm file that you downloaded.
  4. From build 5400 onwards, PAM360 requires an SSL certificate. It imports automatically, but if prompted, click here to download and import it manually.
  5. Click Install in the Update Manager to begin.
  6. To apply multiple upgrade packs, repeat for each (exit Update Manager, start/stop service, repeat).
  7. Once finished, start the PAM360 service.

Note: If using Windows Authentication for MSSQL, start the command prompt using the service account configured for PAM360.

2. Linux

Prerequisites
  • Stop the PAM360 service using /etc/init.d/pam360-service stop.
  • Shutdown the PAM360 service - both primary and secondary, if running (Not applicable for Read-Only servers).
  • Perform a backup of the entire PAM360 installation folder and the PAM360 database.
Steps Required
  1. Navigate to <PAM360_Installation_Folder>/bin using the terminal.
  2. Execute sh UpdateManager.sh -c (CLI mode).
  3. Press i to install and supply the full path of the downloaded .ppm file.
  4. If prompted for an SSL certificate (for build 5400+), download it here and enter its absolute path.
  5. Wait for the "Service Pack applied successfully" message.
  6. To apply multiple upgrade packs, repeat for each.
  7. Start the PAM360 service using /etc/init.d/pam360-service start.