# 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](https://www.manageengine.com/privileged-access-management/upgradepack.html#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 ()](https://www.manageengine.com/privileged-access-management/minor-upgrades.html)

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

## From 8400 to 8500

**SHA256 Checksum:**  
e0edffe18df79586fa126c5e90b1f7fcad0383f6587736b800999f658bcaec3a

[![download-icon](https://www.manageengine.com/privileged-access-management/images/dld.png) Upgrade Pack](https://www.manageengine.com/privileged-access-management/6167/ManageEngine_PAM360_8400_to_8500.ppm)  
[![download-icon](https://www.manageengine.com/privileged-access-management/images/dld.png) Direct Installation](https://archives.manageengine.com/privileged-access-management/8500/)

The following table indicates whether the .ppm file can be applied to PAM360 High Availability servers without reconfiguration for each High Availability architecture and database type.

| High Availability Architecture | Architecture Type | PGSQL | MS SQL |
|---|---|---|---|
| Failover Service (FOS) |  | NA | Yes |
| Application Scaling |  | Yes | Yes |
| Read-Only Server (RO) |  | Yes | NA |
| Secondary Server Model | Secondary Server | Yes | Yes |
| Secondary Server Model | Read-Only Continuity | Yes | NA |

## Upgrade Pack Instructions based on Operating Systems

If you have High Availability servers configured in your environment, refer to [this](https://www.manageengine.com/privileged-access-management/upgradepack.html#pamssc) 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](https://www.manageengine.com/privileged-access-management/help/db-backup-mssql.html) using the SQL studio.

### Steps Required

1. 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.  
   - To identify whether a service account is used or an SQL account is used, navigate to **<PAM360_Installation_Folder>/conf** 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.
3. Click **Browse** and select the **.ppm** file downloaded from the [ManageEngine PAM360 Upgrade Pack](https://www.manageengine.com/privileged-access-management/upgradepack.html) section.
4. From build 5400 onwards, PAM360 requires an SSL certificate for patch integrity verification. Click [here](https://updates.manageengine.com/certificates/latest.crt) to download the SSL certificate if prompted.
5. In the **Import Certificate** pop-up, click **Browse** and **Import** the SSL certificate.
6. Click **Install** to begin the upgrade process.
7. For multiple upgrade packs: exit Update Manager, start & stop the PAM360 service once, and repeat steps 1–3.
8. After finishing, start the PAM360 service.

![Update Manager](https://www.manageengine.com/privileged-access-management/images/updatemanager-1.png)  
![Import Certificate](https://www.manageengine.com/privileged-access-management/images/import-certificate-1.png)

## 2. Linux

### Prerequisites

1. Stop the PAM360 service using:
   ```
   systemctl stop pam360.service
   ```
   **Note:** Ensure **database_params.conf** is in **<PAM360 Installation Folder>/conf/**.
2. Shutdown primary and secondary services (Not applicable for Read-Only servers).  
   **Note:** Ensure PostgreSQL process is not running.
3. Backup the entire PAM360 installation folder and database.  
   **Note:** If using MS SQL, perform a database [backup](https://www.manageengine.com/privileged-access-management/help/db-backup-mssql.html).

### Steps Required

1. Navigate to **<PAM360_Installation_Folder>/bin**.
2. Execute:
   ```
   sh UpdateManager.sh -c
   ```
3. Press `i` to install and provide the full path of the downloaded upgrade package.
4. If prompted, download the SSL certificate from [here](https://updates.manageengine.com/certificates/latest.crt).
5. Enter the certificate's absolute path and wait until **"Service Pack applied successfully"** is displayed.
6. For multiple upgrade packs: exit Update Manager, restart PAM360 service once, and repeat steps 1–3.
7. Start the PAM360 service:
   ```
   /etc/init.d/pam360-service start
   ```

## Applying the PAM360 Upgrade Packs Based on High Availability Server Configurations

### 1. Read-Only Server - PostgreSQL

1. Ensure Read-Only servers are running.
2. Apply the PPM file on the master server.
3. Verify updated build version in **About**.
4. Stop Read-Only servers and start master server.
5. Apply PPM on all Read-Only servers and restart.
6. Upgrade complete.

### 2. Application Scaling

1. Stop main and secondary nodes.
2. Apply PPM to main node, then subnodes.
3. Start all nodes.

### 3. Failover Service - MSSQL

1. Stop slave and primary servers.
2. Apply PPM to primary, then secondary.
3. Restart both.

**Deactivation Command:**
```
UninstallFOS.bat
```

Refer to [FOS Help Guide](https://www.manageengine.com/privileged-access-management/help/failover_service.html).

### 4. Secondary Server Model - MSSQL

1. Apply PPM on primary and secondary.
2. Check replication status.
3. Restart both.

![High Availability - MSSQL](https://www.manageengine.com/privileged-access-management/images/high-availability-mssql.png)

Refer to [High Availability MSSQL Guide](https://www.manageengine.com/privileged-access-management/help/high-availability-mssql.html).

### 5. Secondary Server Model - PostgreSQL

1. Backup all servers.
2. Stop PAM360 on primary and secondary.
3. Ensure PostgreSQL is running on primary.
4. Apply upgrade on primary, then secondary.
5. Restart both.
6. Apply PPM on Read-Only server if applicable.

Refer to [High Availability PostgreSQL Guide](https://www.manageengine.com/privileged-access-management/help/high-availability-postgresql.html).

You have now successfully upgraded PAM360 to the latest version.

For more assistance, please contact our [support team](mailto:pam360-support@manageengine.com).