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.
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 |
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 |
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 |
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.
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.
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 |
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.
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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) |
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.
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.
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) |
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) |
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.
Note: Kindly upgrade to the latest version to setup HA.