ManageEngine® PAM360 Upgrade Pack Download

The latest PAM360 version is  . If you are using an earlier version, you need to apply upgrade pack (Upgrade Instructions).

Download Upgrade Pack | Minor release ( )

Note: We strongly recommend you take a backup before migrating your data to prevent any accidental data loss.

From 6400 to 6500

SHA256 Checksum:
f6ac1c771864a22d4ec9254bac74a6a4bb402a182fe36306f0181b239fcb9725

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)
Read-Only Server (RO)   NA

From 6300 to 6400

SHA256 Checksum:
edf8b7ebd7d546949101c37798d35e1af8938a39f7477605b8e4ab28e040e8ad

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
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

SHA256 Checksum:
93e12f28c46c6d7467dba2f360efde3ef8073bec752dcc4d2ffe1fed7fe73b3a

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling NA
High Availability (HA)
Read-Only Server (RO)   NA

From 6100 to 6200

SHA256 Checksum:
fa326d30370f5699bc975ba330b1f370cbcd7114d27d9406fdd5f9b7ebf7f823

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling NA
High Availability (HA)
Read-Only Server (RO)   NA

From 6000 to 6100

SHA256 Checksum:
ea92a064076e53d0823e0ca76744b4e52bed60173d3a1f0746a42594887ecb3f

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling NA
High Availability (HA)
Read-Only Server (RO)   NA

From 5950 to 6000

SHA256 Checksum:
15c1057526095d08a58c1241f6e80ec1dc7c61e4d984d30b4587800994d23f92

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling NA
High Availability (HA)
Read-Only Server (RO)   NA

From 5900 to 5950

SHA256 Checksum:
345250bdbb8a9f9331753bfc123c016ded152df87de43f7cb65e65a23e105314

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling NA
High Availability (HA)
Read-Only Server (RO)   NA

From 5800 to 5900

SHA256 Checksum:
f5dd8be01602840eaa0eb95c40e9f496a609a87c56d6257325a6ec19d3175890

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling NA
High Availability (HA)
Read-Only Server (RO)   NA

From 5700 to 5800

SHA256 Checksum:
02de2f7972cebbd86bbe8a61c5e8f3781079a6bba6db4f77adc2dd8ed53c03aa

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling NA
High Availability (HA)
Read-Only Server (RO)   NA

From 5600 to 5700

SHA256 Checksum:
c425708b116a4da79ba0e07b658d2966e1e2bd1ee259f36354fe7a667ab3c63e

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling NA
High Availability (HA)

From 5500 to 5600

SHA256 Checksum:
2caffd7dfe22ef3a8edb032488c6cbb1be998037dbb9780a6bfa079d6019df8c

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling NA
High Availability (HA)

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

SHA256 Checksum:
e6c42cd6e483681c61c49606349cc3f0970b47f82ccf4265bcbfbe28f79378c1

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling NA
High Availability (HA)

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

SHA256 Checksum:
76f9e9ff08ae7e0d3688c0208fb26d7057478aed946ed2bced2b49556c61f51c

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling NA
High Availability (HA)

From 5200 to 5300

SHA256 Checksum:
7b93bd6d6b099f13ed6d810ec0defaaa878ee64f87a6c031d4b8f6a9d29d4ba5

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling
High Availability (HA)

From 5100 to 5200

SHA256 Checksum:
23f9b8cb56416048ca97b30aa0ae19691e7a3dd00c0af320cad4d55e66c1189e

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 Support to apply the .ppm file on the secondary PAM360 server without reconfiguring high availability
PGSQL MS SQL
Failover Service (FOS) NA
Application Scaling NA
High Availability (HA)

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

SHA256 Checksum:
f58db4b9e46129ddeaa429dc089d73abfa7d30ac2a69dabd896a53d0a7278173

From 4500 / 4501 to 5000

MD5SUM:
1eb9c094abd2f5b3ff24c1741b537918

From 4100 / 4101 to 4500

MD5SUM:
211a0ddde1f5ee34c78e49b8dc711b68

From 4000 / 4001 / 4002 to 4100

MD5SUM:
355aa1364063ebe5e85ad24f35dbce83

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