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:

Current buildUpgrade path to the latest buildSHA256 Value
8400- Install the service pack to move to build 8500.e0edffe18df79586fa126c5e90b1f7fcad0383f6587736b800999f658bcaec3a
8300- Install the service pack to move to build 8400.37737e2d37f87ba311090894b2c91a8abbd9468af679bb413f6d6a6234e6d7b3
8200- Install the service pack to move to build 8300.451e411730b9103134d9787ef463cd4bba287e6702a356e0e51a848ece0d9fdd
8100- Install the service pack to move to build 8200.52b308c9161c143c03d99dad68de8002d42bde59f69d849eab3e90e93072212a
8000- Install the service pack to move to build 8100.a0d4e951dd604ac199ee5d56c6fb08a6f6610c2fb63d3a6a660b4116db7ee54e
7500- Install the service pack to move to build 8000.cebed8bc5cb1ea28828ee4d0d050d2db84cd10c8d0b9b9751b62a67a27435315
7400- Install the service pack to move to build 7500.d10f7c919191cb60b55cc91a8afffdc1a07f8432472381f4cdb7ef13083383e3
7300- Install the service pack to move to build 7400.2e8d320f35a5306343b62d80e11d84dce34399988027cdd9c450a61daeb7518d
7200- Install the service pack to move to build 7300.f6c53eff562a2e2391a6691ac73ffe45bf291fd134f3e757fd8ce544dfd0bd8e
7100- Install the service pack to move to build 7200.a5869020212d4043457be2980f940d86a82b24f582c328125d3ce330d8f3cdbc
7000- Install the service pack to move to build 7100.da3e3157ed1744c804f30525ad102d7f3dc2cec53d15dbc88729f8070773f13d
6700- Install the service pack to move to build 7000.70a4229f97b66e7d8277ea44e5209cf94336ce6620981c681834c4e9ede8f2f5
6600- Install the service pack to move to build 6700.b866e33ea5186795a9c2f2a357bec21f182420f55d1503614748dc112bd7f384
6500- Install the service pack to move to build 6600.70df1c0d6788a8edaa3a34726df312272517668e977ec29fcbec72bf90213c0a
6400- Install the service pack to move to build 6500.1865e8cae8c68436892f8c0468ac8de7ab2261d6f989e362f8937c7739c60f09
6300- Install the service pack to move to build 6400.7284fb97e6937b5bf9b47c25f8bb584f5f38c81a25b4c39674bf46d8a124b46c
6200- Install the service pack to move to build 6300.cc75762842ed5b537fecb5900c9b89b6a1ad733722a35d40643b74424b624d6a
6100- Install the service pack to move to build 6200.a8cfb604db1bcc7eeaff8f5c37262e211a200bfb140fc3192f239109a6b24df8
6000- Install the service pack to move to build 6100.91f54ac0e156454b4eeecdadf32dc236e0e1d5860a8b7d275a61b2c5b5d1eb1c
5950- Install the service pack to move to build 6000.bde248be2ef65f9c168236ede8cbcd21073acd85ab26f6a7d7f86393513d4cfa
5900- Install the service pack to move to build 5950.345250bdbb8a9f9331753bfc123c016ded152df87de43f7cb65e65a23e105314
5800- Install the service pack to move to build 5900.46e810bf0fa08caae676369a9c7144a282d4c23e0244fbd739c4bc4de4a27e64
5700- Install the service pack to move to build 5800.0b707f9e79fe518177b60b5ad33635503b356e7128bd9b447f48f6b58a3b4741
5600- Install the service pack to move to build 5700.e3a067d5917d5311898229b2d0b8cca1c1cff103fc2f45ac747f5dec505d030e
5500- Install the service pack to move to build 5600.d0ab8e2cd7f11e32c1490ed9ae7880f09cbff9dc975d0b986e653342d174ad88
5400- Install the service pack to move to build 5500.553b8669f97ab08e0b2fc4e680dace53de1d852a073cc9d5ce05fbe71004dc33
5300- Install the service pack to move to build 5400.5c51b886e682839835eb87dd5a321d8820e0031e12b8ecaa02898c141adba761
5200- Install the service pack to move to build 5300.7b93bd6d6b099f13ed6d810ec0defaaa878ee64f87a6c031d4b8f6a9d29d4ba5
5100- Install the service pack to move to build 5200.23f9b8cb56416048ca97b30aa0ae19691e7a3dd00c0af320cad4d55e66c1189e

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.