CA PAM Tech Tip by Miquel Gilibert i Sunyé, Principal Support Engineer for March 27, 2017
Sometimes one tries to publish a remote application and run it as a RDP service from PAM, but that does not work. This occurs typically with bat files starting java applications or with command line utilities, but these may not be the only applications affected.
The observed behavior is that the remote machine opens the RDP console normally, but then when it should be running the remote utility, which has been otherwise correctly published as a remote application in the Remote Desktop, the session closes and nothing is run
On the other hand, if one accesses the remote server using RDP and then runs the same bat or application, just like one would do logging normally to the system, this works just fine.
The reason for this lies in the fact that when we are logging in to the remote windows system from PAM, we are opening the session in the default working directory. This is C:\Windows\System32.
If the application or batch we intend to run work fine from there by running it just as specified in the PAM configuration for the service, then running the published application from PAM as a RDP service will work. If not, then likely the script will never be run and it will log out us from the remote server.