- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
05-20-2019 01:05 AM
Hi,
I do an connection via RDP to the Remote Server, so far it's fine. But I need to run a local App on this Server, this did not work.
I use the Standard RDP Connection Component and change the ClientInvokeType to CommandLine, add the CleintSpezific Property StartProgram and ClientInstallationPath.
Do anybody know how to get it work?
Cheers,
Thomas
05-20-2019 02:13 AM
Well, something are made to work specifically they are made for. Changing RDP connection component will not work.
For that purpose, either you make a custom connector using Autoit or use sample connection component provided ootb.
Thanks,
05-20-2019 02:13 AM
Well, something are made to work specifically they are made for. Changing RDP connection component will not work.
For that purpose, either you make a custom connector using Autoit or use sample connection component provided ootb.
Thanks,
05-20-2019 02:13 AM
Well, something are made to work specifically they are made for. Changing RDP connection component will not work.
For that purpose, either you make a custom connector using Autoit or use sample connection component provided ootb.
Thanks,
05-20-2019 06:17 AM
You can try "Custom Code" future of PSM where you can call your Remote server client app before the PSM session begins or after it ends. There is example you can leverage, this is worth to try and you can use this approach for any client components.. Good Luck!
06-28-2019 12:49 AM
Thanks all, thanks @Himanshu Pandey I have managed it.
06-28-2019 12:50 AM
would you mind sharing what you managed for reference to others?
06-28-2019 12:50 AM
would you mind sharing what you managed for reference to others?
06-28-2019 01:12 AM
I try to describe my problem. We also have the requirement to work on CyberArk ourselves, so we need to access the test environment via the production environment. In the case of the private ark client this resulted in the following problem, the vault carries in the standard always the name of the domain, so the name for test and prod was identical. Through a Global Config with two Vaults now called PROD and TEST, we managed to see and edit both Vaults in Private Ark Cleint. My Connection Component only starts the Private Ark Client which is installed on the PSM and via AutoIt Mouse Magic 🙂 and a new property that holds the target information the script opens the desired Vault. Thus, we ourselves do not need to know the Vault passwords anymore and can manage them. Problem solved.
06-28-2019 01:14 AM
Done very well, good to know!
06-28-2019 01:14 AM
Done very well, good to know!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

