Failing to configure transparent login with application that spawn another process when it starts up.
At this point of time, CA PAM/ transparent login does not support use cases where batch file (.bat) or native launcher (.exe) starts up another (actual) application. This is because the Launch Path defined in RDP Application setup (Services >> RDP Applications) does not match with the actual application's launch path.
Release: PAMDKT99500-2.7-Privileged Access Manager-NSX API PROXY
Create a custom Java launcher (.jar) for the application and specify the Launch Path in RDP Application with the following format:
"<actual application>" -jar <custom Java launcher>
For example: "C:\Program Files (x86)\Java\jre1.8.0_101\bin\javaw.exe" -jar C:\LocalAdmin\LocalAdmin.jar
Troubleshooting Windows transparent login problems passing data to backend: