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

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

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

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