ManageEngine® PAM360 Upgrade Pack Download

The latest PAM360 version is 5300. If you are using an earlier version, you need to apply upgrade pack.

Download Upgrade Pack

Note: We strongly recommend you take a backup before migrating your data to prevent any accidental data loss.
From 5200 to 5300 Upgrade pack 5200 to 5300
SHA256 Checksum:
7b93bd6d6b099f13ed6d810ec0defaaa878ee64f87a6c031d4b8f6a9d29d4ba5

High Availability (HA) Setup

Direct installation file for 5300

Note: If you've configured HA for your PAM360 instance, your secondary application server should always run the same version as your primary server. For instance, if you're upgrading to 5300, you should concurrently reconfigure HA and set up a fresh secondary instance that runs 5300. Additionally, ensure that the software architectures are also the same.

From 5100 to 5200 Upgrade pack 5100 to 5200
SHA256 Checksum:
92c384f8d8301e9b426684cc8a473769a5b3831a60e6fd477647408c7714c3c7

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.
Direct installation file for 5200
From 5000 / 5001 / 5002 / 5003 / 5004 to 5100 Upgrade pack 5000 / 5001 / 5002 / 5003 / 5004 to 5100
SHA256 Checksum:
f58db4b9e46129ddeaa429dc089d73abfa7d30ac2a69dabd896a53d0a7278173
Direct installation file for 5100
From 4500 / 4501 to 5000 Upgrade pack 4500 / 4501 to 5000
(1eb9c094abd2f5b3ff24c1741b537918)
Direct installation file for 5000
From 4100 / 4101 to 4500 Upgrade pack 4100 / 4101 to 4500
(211a0ddde1f5ee34c78e49b8dc711b68)

Direct installation file for 4500

From 4000 / 4001 / 4002 to 4100 Upgrade pack 4000 / 4001 / 4002 to 4100
(355aa1364063ebe5e85ad24f35dbce83)
Kindly upgrade to the latest version to setup HA.

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.

Applying the Upgrade Pack

Windows (PostgreSQL)

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. Shut down the PAM360 service - both primary and secondary, if running. Also, make sure that the Postgres process is not running in the task manager.
  3. Take a backup of the entire PAM360 installation folder, and store it somewhere safe. You can revert to this copy in case of an upgrade failure, with your settings intact.

Steps Required

Note: If you have configured HA, the following steps will be applicable for the Primary Server.

  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'.
  3. Click 'Browse', select the '.ppm' file that you downloaded, and Install.
  4. 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.
  5. Once you have finished applying the upgrade packs, start the PAM360 service.

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

Steps Required - Secondary Server

For the secondary instance, check if the existing .ppm file can be applied to your newer version from here. If the secondary .ppm file is applicable, please follow the steps under the previous section and proceed. Else, you will have to reconfigure or reinstall HA in the secondary instance.

For the steps to reconfigure HA and set up a fresh secondary instance of PAM360, click here.

 

Windows (MS SQL)

Prerequisites

  1. Stop the PAM360 service and exit the tray icon.
  2. Shut down the PAM360 service - both primary and secondary, if running.
  3. Do a backup of the entire PAM360 installation folder, and store it somewhere 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.

Steps Required

Note: If you have configured HA, the following steps will be applicable for the Primary Server.

  1. Navigate to <PAM_Installation_Folder>/bin directory from CMD and execute UpdateManager.bat
    • During MS SQL server configuration for 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 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.
  2. Click Browse and select the .ppm file that you downloaded. Then, Install.
  3. 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.
  4. After applying the upgrade packs, start the PAM360 service.

If you need any assistance or clarifications, please contact pam360-support@manageengine.com.

Steps Required - Secondary Server

Additionally, to configure High Availability, 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 in the screenshots 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.

    Deleting Subscription
  2. Deleting Publication
    Again, 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.

    Deleting Publication
  3. Disabling Publishing Distribution
    Now, right click the 'Replication' folder and click the option 'Disable Publishing and Distribution'.

    Disabling Publishing Distribution

    Now, proceed applying the upgrade pack.

For the secondary instance, check if the existing .ppm file can be applied to your newer version from here. If the secondary .ppm file is applicable, please follow the steps under the previous section and proceed. Else, you will have to reconfigure or reinstall HA in the secondary instance.

To reconfigure HA and set up a fresh secondary instance of PAM360, follow the steps given here.

 

Linux (Headless)

Prerequisites

  1. Stop 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. Shut down PAM360 service - both primary and secondary, if running. Also, make sure that the postgres process is not running in task manager.
  3. Take 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.

Steps Required

Note: If you have configured HA, the following steps will be applicable for the Primary Server.

  1. Navigate to <PAM360_Installation_Folder>/bin directory using terminal.
  2. Execute the command sh UpdateManager.sh -c (This will run the Update Manager in CLI mode)
  3. Now, press i to install. Supply full path of the upgrade pack and wait for the upgrade to complete until the message 'Service Pack applied successfully' is displayed.
  4. 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.
  5. After applying the upgrade packs, start the PAM360 service, using /etc/init.d/pam360-service start

If you need any assistance or clarifications, please contact pam360-support@manageengine.com.

Steps Required - Secondary Server

For the secondary instance, check if the existing .ppm file can be applied to your newer version from here. If the secondary .ppm file is applicable, please follow the steps under the previous section and proceed. Else, you will have to reconfigure or reinstall HA in the Secondary instance.

To reconfigure HA and set up a fresh secondary instance of PAM360, follow the steps given in the help guide: MsSQL | PostgreSQL

 

Upgrading Your Failover Service (FOS) Setup

In a failover service set up, with two application servers bound to an MS SQL cluster, only the primary server can be upgraded directly. The secondary server should be reinstalled, and the failover service setup should be reconfigured.

Here are the sequence of steps to be followed:

Deactivating the Failover Service

You can deactivate the failover service either from the primary or the secondary server.Follow 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.

Next, uninstall the PAM360 application entirely from the other servers.

Upgrading the Primary Server

You can upgrade your primary installation of PAM360 by following the below steps. The latest upgrade packs are available for download here. You can use the instructions mentioned here to apply the upgrade packs one by one to reach the latest version.

Note: If MS SQL is your back end database, do take a backup before proceeding further. This way, even if something goes wrong, you can immediately revert to the existing version by deleting the PAM360 directory and placing the backup in same location to get your PAM360 instance up and running again.

Steps Required

  1. Stop the PAM360 service and exit the tray icon.
  2. Navigate to <PAM360_Installation_Folder>/bin directory from CMD and execute UpdateManager.bat
    • During MS SQL server configuration for 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 a SQL account is used, navigate to <PAM360_Installation_Folder>/conf directory and open 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. Click Browse, select the .ppm file that you downloaded and Install.
  4. To apply multiple upgrade packs, do the following for each upgrade; exit the Update Manager, start & stop the PAM360 service once, and execute the upgrade steps.
  5. After applying the upgrade packs, start the PAM360 service.

Reinstalling PAM360 on the Secondary Server

After upgrading the primary server to the latest version, reinstall the same version of PAM360 on your secondary server. Check if the existing .ppm file can be applied to your newer version from here. If the secondary .ppm file is applicable, please follow the steps under the previous section and proceed. Else, you will have to reinstall the secondary server.

In short, ensure that both your primary and secondary servers always run the same PAM360 version. You can download the required installation files from the upgrade pack table at the top.

Reconfiguring the FOS Service

After reinstalling the secondary server, perform the steps detailed in the failover service help documentation to configure the failover service in the secondary server again.

 

Application Scaling using MS SQL Server

Upgrading the Main Node

Upgrade your main node of PAM360 by following the below steps. Upgrade your main node first followed by the sub nodes. The latest upgrade packs are available for download here. Use the instructions listed here to apply the upgrade packs one by one until you reach the latest version.

Note: If MS SQL is your back end database, do take a backup before proceeding further. This way, even if something goes wrong, you can immediately revert to the existing version by deleting the PAM360 directory and placing the backup in same location to get your PAM360 instance up and running again.

Steps Required

  1. Stop the PAM360 service and exit the tray icon.
  2. Navigate to <PAM360_Installation_Folder>/bin directory from CMD and execute UpdateManager.bat
    • During MS SQL server configuration for PAM360 database, if you have opted for 'Windows Authentication,' you have to 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 a SQL account is used, navigate to <PAM360_Installation_Folder>/conf directory and open 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. Click Browse, select the .ppm file that you downloaded and Install.
  4. To apply multiple upgrade packs, do the following for each upgrade; exit the Update Manager, start & stop the PAM360 service once, and execute the upgrade steps.

After applying the upgrade packs, start the PAM360 service.

Upgrading Sub Node(s)

After upgrading the main node to the latest version, reinstall the same version of PAM360 on your sub node(s). For the sub node, check if the existing .ppm file can be applied for your newer version from here. If the .ppm file is applicable, please follow the steps given under the previous section and proceed. Else, you will have to reinstall the sub nodes.

In short, ensure that both your main node and sub node always run the same PAM360 version. To download the required installation files, scroll up to the upgrade pack table.