- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
05-30-2023 12:54 AM
No matter which EPM policy i have defined to this app installation executable, it never gets it and never get elevated, all other software works fine.
It was tested on numerous computers (win10 OS), it of course works with LAR.
Only thing that is seems strange to me is that Publisher Status states "Signature not Trusted", but it does not suppose to cause EPM not to elevate this software installationPFA this is how it looks even if i add this app install to a policy - keeps on being inside the GreyList.
Policy is still - Windows Main Default Policy.
We are using EPM SaaS latest version 23.4.0.1235.
Also i have tested this Software with EPM-On-Prem agent 11.5.5.102 and added it to Elevated Policy and it worked without issues.
I feel like SaaS default policies needs some adjustment.
Thanks for whom can help.
05-30-2023 04:46 AM
it depends how you created the elevate policy. if you use the publisher attribute in the application definition and this publisher signature is not valid on the endpoint the policy will not be effective.
05-30-2023 04:55 AM
Hi @Yossi Dantes
thank you for your reply, please explain what you mean.
For my case this is what i did:
I have tried a couple of measures by adding that to the predefined Elevate Applications Group:
sometimes all of them, sometimes only 2 of them, sometimes only 1 of them but nothing changed.
Any ideas?
05-30-2023 04:57 AM
are you sure the agent received the policy? when you right click on the agent icon -> about, does it seems the agent get policies lately?
05-30-2023 04:58 AM
I'm sure! this is not my first rodeo 🙂
Thank you @Yossi Dantes for helping out!
05-30-2023 05:03 AM
according to the screenshot you attached the EPM agent doesn't apply the policy you defined on the DockerToolbox-19.03.1.exe file. if you absolutely sure you defined the policy correctly and target it to the correct endpoint/user, please collect agent logs and open a case with customer support.
05-31-2023 05:35 AM
We faced the same issue with another application called OfficeTimelinePro. The root cause turned out that the publisher certificate on the executable and the certificate installed on the OS had different thumprints. One thing to keep in mind is that a visual inspection of the certificate chain on the OS does not indicate a problem. It's only when you notice the finer details and look at the thumbprint specifically, then you start noticing the difference.
In our case, including the "Publisher" criteria while creating the application definition never worked for that application. We could only get that application to elevate with a broad definition.
You could try running this command and attach it to your support case - C:\Program Files\CyberArk\Endpoint Privilege Manager\Agent\vf_agent.exe -DumpFileInfo "<<path of Docker Toolbox>>" c:\temp\output.txt
06-01-2023 01:14 AM
Thanks @Nikhil Rao - i will do that!
Appreciate the help.
06-02-2023 03:38 AM
Good Advice @Nikhil Rao
11-12-2024 03:33 PM
Is there a way we can find the publisher status remotely rather than going into the endpoint?
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!

