PAM Client on Windows OS - upgrade from 4.0.2 to 4.1.3

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

Client has 17 PAM Clusters and each Cluster with 2 PAM nodes. Totaling 34 PAM Appliances in Vmware.

They would start the upgrade from version 4.0.2 gradually keeping during transition until all pam nodes are upgraded the pam client 4.0.2 and 4.1.3 working for the same Windows machine.

 

 

 

Environment

Release : 4.0

Resolution

Every time we are on 4.0.2 and we go to 4.1.3 and again we go back to 4.0.2 it is working without problems if user access the new 4.1.3 PAM node will receive message of version Change and if accept will update the PAM client. When accessing 4.0.2 the process will be the same.

Wait the update process to finish until 100%

It's always good before and after updating the PAM Client connecting to a PAM server with a different version the first time, closing the client and reopening it to ensure closing a lock file that the PAM Client creates in tmp folder

Additional Information

• Version 4.1.3 is a milestone as it changes the PAM Client to 64 bits and has Java 17 built-in while previous versions has Java 8 build-in
  
  
• In case you want to install the PAM Client 4.1.3 separately, use the browser to access the 4.1.3 server and download the CAPAMClientInstall_V4.1.3.exe file.
  Version 4.1.3 is installed by default under C:\Program Files\PAM Client unlike previous versions which were installed under C:\Program Files(x86)\PAM Clien