The installation must be performed using a non-root account that has root or sudo privileges.
The logged in account should have permission to the installation directory.
The file should have execute permissions and to provide this you can run the command chmod a+x <file-name>. For example, chmod a+x ManageEngine_PAM360.bin
While installing in a headless server (no GUI), use the command ./ManageEngine_PAM360.bin -i console.This will start the installation in CLI mode.
The most common issues with the service startup are the key file not being present in the correct path and folder permissions being incorrect. Check the PAM360/logs/wrapper.log file and you will see the root cause. If you see the error regarding key ...
Check if the logged in account has local admin rights on the server since it is required for the installation to complete. Check if the logged in account has write permission to the installation directory and temp %temp% directories. If the ...
Generally LDAP option is used only if the customer has PAM360 installed on a Linux server. Check with the customer for the reason for installing PAM360 on a Linux server and inform them that they will have to install the Agents on ALL windows ...