Upgrade Pack
Home » Upgrade Pack

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).

How Do I Find My Build Number?

Log in to PAM360. Click the 'user profile' icon at the top right corner of the web console and click 'About'. In the new window that opens up, you will find the build number of your currently installed PAM360 setup below the version number.

Download Upgrade Pack | Minor release ( )

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

From 7200 to 7300

SHA256 Checksum:
f6c53eff562a2e2391a6691ac73ffe45bf291fd134f3e757fd8ce544dfd0bd8e
download-icon 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 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 7100 to 7200

SHA256 Checksum:
a5869020212d4043457be2980f940d86a82b24f582c328125d3ce330d8f3cdbc
download-icon 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 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 7000 to 7100

SHA256 Checksum:
da3e3157ed1744c804f30525ad102d7f3dc2cec53d15dbc88729f8070773f13d
download-icon Upgrade Pack download-icon 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 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 6700 to 7000

SHA256 Checksum:
70a4229f97b66e7d8277ea44e5209cf94336ce6620981c681834c4e9ede8f2f5
download-icon Upgrade Pack download-icon 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 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 6600 to 6700

SHA256 Checksum:
b866e33ea5186795a9c2f2a357bec21f182420f55d1503614748dc112bd7f384
download-icon Upgrade Pack download-icon 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 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: 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

SHA256 Checksum:
70df1c0d6788a8edaa3a34726df312272517668e977ec29fcbec72bf90213c0a
download-icon Upgrade Pack download-icon 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 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: 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

SHA256 Checksum:
f6ac1c771864a22d4ec9254bac74a6a4bb402a182fe36306f0181b239fcb9725
download-icon Upgrade Pack download-icon 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 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
download-icon Upgrade Pack download-icon 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 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
download-icon Upgrade Pack download-icon 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 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
download-icon Upgrade Pack download-icon 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 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
download-icon Upgrade Pack download-icon 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 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
download-icon Upgrade Pack download-icon 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 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
download-icon Upgrade Pack download-icon 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 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
download-icon Upgrade Pack download-icon 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 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
download-icon Upgrade Pack download-icon 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 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
download-icon Upgrade Pack download-icon 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 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
download-icon Upgrade Pack download-icon 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 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
download-icon Upgrade Pack download-icon 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 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)

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
download-icon Upgrade Pack download-icon 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 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
download-icon Upgrade Pack download-icon 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 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 5100 to 5200

SHA256 Checksum:
23f9b8cb56416048ca97b30aa0ae19691e7a3dd00c0af320cad4d55e66c1189e
download-icon Upgrade Pack download-icon 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 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
download-icon Upgrade Pack download-icon Direct Installation

From 4500 / 4501 to 5000

MD5SUM:
1eb9c094abd2f5b3ff24c1741b537918
download-icon Upgrade Pack download-icon Direct Installation

From 4100 / 4101 to 4500

MD5SUM:
211a0ddde1f5ee34c78e49b8dc711b68
download-icon Upgrade Pack download-icon Direct Installation

From 4000 / 4001 / 4002 to 4100

MD5SUM:
355aa1364063ebe5e85ad24f35dbce83
download-icon Upgrade Pack download-icon 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

  1. 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.
  2. Shutdown the PAM360 service - both primary and secondary, if running (Not applicable for Read-Only servers).
    Notes:
    • If you are using PostgreSQL as the database, ensure that the Postgres process is not running in the task manager.
    • If you are using MSSQL as the database, ensure that the OpenJDK/Zulu platform process is not running in the task manager.
  3. Perform a backup of the entire PAM360 installation folder, and store it someplace safe. You can revert to this copy in case of an upgrade failure with your settings intact. Additionally, take a backup of the PAM360 database.
    Note: If you are using MS SQL as the database, perform a database backup using the SQL studio.

Steps Required

  1. To start with, right-click the Command Prompt and select 'run as administrator'.
  2. Navigate to the '<PAM360_Installation_Folder>/bin' directory and execute 'UpdateManager.bat'.
    • During MS SQL server configuration for the PAM360 database, if you have opted for 'Windows Authentication,' start the command prompt using the service account with which the PAM360 service has been configured to connect to the SQL server (i.e., instead of running as administrator, run as the service account).
    • To identify whether a service account is used or an SQL account is used, navigate to <PAM360_Installation_Folder>/conf directory and open the database_params.conf file. If you do not find a username and password in the file, then PAM360 is using Windows Authentication, and therefore you need to run the command prompt with service account privilege.
    3. Update Manager
  3. Click Browse and select the .ppm file that you downloaded from the ManageEngine PAM360 Upgrade Pack section
  4. As a part of patch integrity verification from PAM360 build 5400 onwards, PAM360 requires an SSL certificate to complete the upgrade process. PAM360 will automatically import this certificate during the upgrade. In case, if the automatic import does not happen, you will be prompted to manually add the SSL certificate. Download the relevant SSL certificate using the links below:
    1. For upgrade packs up to 6520, click here.
    2. For upgrade pack after 6520, click here.
  5. In this case, when the Import Certificate pop-up opens, click Browse and Import the SSL certificate you downloaded from the above step.
    6. Import Certidficate
  6. Click Install in the Update Manager window to begin the upgrade process. Please note that importing the SSL certificate is mandatory while upgrading PAM360 from version 5.3 to 5.4. However, this is a one-time operation and you need not repeat the process during the next version upgrade.
  7. To apply multiple upgrade packs, do the following for each upgrade; exit the Update Manager, start & stop the PAM360 service once, and execute the above steps 1, 2, and 3.
  8. Once you have finished applying the upgrade packs, start the PAM360 service.

2. Linux

Prerequisites

  1. Stop the PAM360 service using the command /etc/init.d/pam360-service stop.
    Note: In case you store the 'database_params.conf' file at a different location, copy the file back to the original location (i.e., <PAM360 Installation Folder>/conf/ ) before performing the upgrade.
  2. Shutdown the PAM360 service - both primary and secondary, if running (Not applicable for Read-Only servers).
    Note: If you are using PostgreSQL as the database, ensure that the Postgres process is not running in the task manager.
  3. Perform a backup of the entire PAM360 installation folder and store it in some other location. In case something goes wrong with the upgrade, you can revert to this copy with your settings intact. Additionally, take a backup of the PAM360 database.
    Note: If you are using MS SQL as the database, perform a database backup using the SQL studio.

Steps Required

  1. Navigate to <PAM360_Installation_Folder>/bin directory using the terminal.
  2. Execute the command sh UpdateManager.sh -c(This will run the Update Manager in CLI mode)
  3. Now, press i to install and supply the full path of the upgrade package that you have downloaded from ManageEngine PAM360 Upgrade Pack section.
  4. As a part of patch integrity verification from PAM360 build 5400 onwards, PAM360 requires an SSL certificate to complete the upgrade process. PAM360 will automatically import this certificate during the upgrade. In case, if the automatic import does not happen, you will be prompted to manually add the SSL certificate. Download the relevant SSL certificate using the links below:
    1. For upgrade packs up to 6520, click here.
    2. For upgrade pack after 6520, click here.
  5. Enter the SSL certificate's absolute path when prompted. Once the certificate is imported successfully, wait for the upgrade to complete until the message "Service Pack applied successfully" is displayed.
    Please note that the SSL certificate import is a one-time operation, and you need not repeat the process during the next version upgrade.
  6. To apply multiple upgrade packs, do the following for each upgrade; exit the Update Manager, start & stop the PAM360 service once, and execute the above steps 1, 2, and 3.
  7. After applying the upgrade packs, start the PAM360 service using /etc/init.d/pam360-service start

Applying the PAM360 Upgrade Packs Based on Secondary Server Configurations

1. Read-Only Server - PostgreSQL

  1. Ensure that the Read-Only servers are up and running.
  2. Apply the PPM file in the master server using the above instructions based on your operating system.
  3. Post applying the PPM in the master server, log in to the Read-Only server(s) and verify for the updated build version in the About to ensure a proper database update.
    Note: The above steps only update the Read-Only server database and do not have any changes in the PAM360 application setup. To upgrade the PAM360 application in the Read-Only server to the recent version, apply the PPM in all available Read-Only servers.
  4. Now, stop all the Read-Only server(s) and start the master server.
  5. Apply the PPM file one by one in all the available Read-Only server(s) using the above instructions based on your operating system and start all the Read-Only server(s).
  6. Now, you have successfully upgraded to the latest version of PAM360 configured with the Read-Only server(s) setup.

2. Application Scaling

If you have Application Scaling configured in your environment, upgrade your main node first followed by the subnodes. For the subnodes (secondary server), check if the existing .ppm file can be applied to your newer version from the ManageEngine PAM360 Upgrade Pack section. If the .ppm file is applicable, please follow the steps given below and proceed. Else, you will have to reconfigure the subnodes.

  1. Stop the main node and the configured secondary nodes of PAM360.
  2. Apply the PPM file in the main node and then to the subnodes one by one using the above instructions based on your operating system.
  3. Now, start the PAM360 main node and the available subnodes.

3. Failover Service - MSSQL

For the secondary instance configured as a failover service, check if the existing .ppm file can be applied to your newer version from the ManageEngine PAM360 Upgrade Pack section. If the secondary .ppm file is applicable, please follow the instruction and proceed. Else, you will have to reconfigure a fresh failover service in the secondary instance by following the deactivation steps given below the upgrade steps.

  1. Stop the slave server as it needs to be in a slave state and the primary server.
  2. Apply the PPM file to the primary server and then to the secondary using the above instructions based on your operating system.
  3. Now, start the PAM360 master and slave servers.

Deactivating the Failover Service

You can deactivate the failover service either from the primary or the secondary server by following the below steps:

  1. Open a command prompt in any of the servers.
  2. Navigate to <PAM360_SERVER_HOME>\bin directory.
  3. Execute the command: UninstallFOS.bat.
  4. Now, uninstall the PAM360 application entirely from the other servers.To reconfigure a failover service and set up a fresh secondary instance of PAM360, follow the steps given in the help guide: FOS.

4. High Availability - MSSQL

For the secondary instance, check if the existing .ppm file can be applied to your newer version from the ManageEngine PAM360 Upgrade Pack section. If the secondary .ppm file is applicable, please follow the instruction and proceed. Else, you will have to reconfigure or reinstall High Availability in the secondary instance by following the prerequisites given below the upgrade instructions.

  1. Apply the PPM file in the primary server and the secondary server using the above instructions based on your operating system.
  2. Now, check the replication status in the primary server in (local publication >> view synchronization status), and it should be shown as below.
    3. High Availability - MSSQL
  3. Now, start the PAM360 secondary and the primary servers.

Prerequisites for Reconfiguring High Availability

To reconfigure a new High Availability instance, delete the replication data related to 'Subscriptions' and ''Publications', and disable 'Publishing and Distribution'. To do so, log in to MS SQL Server Management Studio and delete the following files/folders as explained below: (Skip these steps if High Availability is not configured).

  1. Deleting Subscription
    Navigate to Replication >> Local Publications >> <Name of PAM360 database:PAM360-HA >. You will see a file with <PAM360 server name>:<Name of PAM360 database>. Right-click the file and press 'Delete' in the menu.
  2. Deleting Publication
    Navigate to Replication >> Local Publications >> <Name of PAM360 database:PAM360-HA>. Right-click the folder <Name of PAM360 database: PAM360-HA> and press 'Delete' in the menu.
  3. Disabling Publishing Distribution
    Now, right-click the 'Replication' folder and click the option 'Disable Publishing and Distribution'. Further, proceed with the configuration steps given in the help guide to reconfigure the High Availability.

5. High Availability - PostgreSQL

For the secondary instance, check if the existing .ppm file can be applied to your newer version from the ManageEngine PAM360 Upgrade Pack section. If the secondary .ppm file is applicable, apply the PPM file in the primary server and the secondary server using the above instructions based on your operating system. Else, you will have to reconfigure or reinstall High Availability in the secondary instance.

To reconfigure High Availability and set up a fresh secondary instance of PAM360, follow the steps given in the help guide: PgSQL.

For more assistance, please get in touch with our Support team pam360-support@manageengine.com.

Quick Links