- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
05-24-2023 12:18 PM
At my company we use a program called PrinterLogic to assist end users with adding printers to their computers. It makes it very simple and it's a program we want to keep using. However, after rolling out CyberArk, this program is now broken because it uses elevated CMD. We want to block elevated CMD unless it is required for use by an approved program (such as PrinterLogic). So my question is what can I configure within CyberArk to get this to work as intended? As of right now CMD elevated is blocked entirely (prompting UAC).
05-24-2023 10:34 PM
Hi @Drew Reisner,
You can try to apply the policy with Child processes.
Child processes apply the policy to the immediate children of an elevated process, and also to their children (all descendants).
Thanks,
Tamir
05-24-2023 10:34 PM
Hi @Drew Reisner,
You can try to apply the policy with Child processes.
Child processes apply the policy to the immediate children of an elevated process, and also to their children (all descendants).
Thanks,
Tamir
05-26-2023 02:50 PM
You can search what arguments the application use to launch CMD elevated, and create a policy that contains the elevation to CMD only in the case of the arguments of the application is present. The CMD with no arguments may still on allow applications, to run normally.
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!

