<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article EPM - Troubleshoot wrong policy applying in Endpoint Privilege Manager (EPM) Articles</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/epm-troubleshoot-wrong-policy-applying/ta-p/1428375</link>
    <description>The article will provide some steps you can take to troubleshoot why the wrong policy is applying.&lt;BR /&gt;&lt;BR /&gt;Generally, these are the reason another policy is applying instead of your desired policy:&lt;BR /&gt;&lt;BR /&gt;A) The unwanted policy has a higher priority.&lt;BR /&gt;B) The unwanted policy has a definition with child processes enabled and it applies to the parent process.&lt;BR /&gt;C) The desired policy has targeting that does not match.&lt;BR /&gt;D) The desired policy has definition properties that do not match.&lt;BR /&gt;E) The desired policy has condition settings which do not match.&lt;BR /&gt;F) The unwanted policy has exactly the same priority as the desired policy.&lt;BR /&gt;G) The endpoint has not downloaded the desired policy from the EPM SaaS server.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Try to rule out each of the above possible causes until you narrow down the cause,

&lt;H3&gt;Steps&lt;/H3&gt;
A) The unwanted policy has a higher priority.&lt;BR /&gt;- Generate SupportInfo logs.&amp;nbsp;&lt;BR /&gt;-&amp;nbsp;Open the SupportInfo zip and open vf_agent_srv.trace using notepad.&amp;nbsp; Find the PROCSTART event for the process launch and get the name of the unwanted policy which is applying.&lt;BR /&gt;- In the SupportInfo zip&amp;nbsp;look in the trace subfolder.&amp;nbsp; Open vf_policies.xml using a web browser.&amp;nbsp;&lt;BR /&gt;- Search for the name of your desired policy.&amp;nbsp; Then find the "order" of that policy, which is the priority&lt;BR /&gt;- Search for the name of the policy which is actually applying on launch.&amp;nbsp; Check the "order" of that policy.&lt;BR /&gt;- Lower "order" numbers have a higher priority.&amp;nbsp; So you can either confirm that this is the possible cause, or you can rule out this as the cause.&lt;BR /&gt;&lt;BR /&gt;B) The unwanted policy has a definition with child processes enabled and it applies to the parent process.&lt;BR /&gt;- In the SupportInfo zip look at the PROCSTART event for the process launch.&amp;nbsp;&lt;BR /&gt;- If you don't see "Inherited from" you can rule this out as a possible cause&lt;BR /&gt;- If you see "Inherited from", then you need to find the parent process.&amp;nbsp; Look at "Parent=" and take that number.&amp;nbsp; Search backwards until you find a "PID=" number which matches.&amp;nbsp; Check if that PROCSTART process launch says "Inheritable".&amp;nbsp; If it doesn't saw "Inheritable" then keep repeating until you find the reason that the intended policy is not applying.&amp;nbsp; You can then consider if you should have child processes enabled on the policy definition/&lt;BR /&gt;&lt;BR /&gt;C) The desired policy has targeting that does not match.&lt;BR /&gt;- In vf_policies.xml, find the desired policy.&amp;nbsp; Check at the top of that policy's xml to see if there is any user or computer group targeting.&amp;nbsp; It may look like this:&lt;BR /&gt;&amp;lt;UserGroupList&amp;gt;&lt;BR /&gt;&amp;lt;User accountType="User"&amp;gt;Domain\joe.smith&amp;lt;/User&amp;gt;&lt;BR /&gt;&amp;lt;/UserGroupList&amp;gt;&lt;BR /&gt;- check to see if it is matches the user who is launching the app&lt;BR /&gt;- Note in the above example, there is no SID.&amp;nbsp; If you think this could be a possible cause you can use the EPM Admin Utility to add the targeting to the policy.&amp;nbsp; When you do this, it will attach the SID to the policy xml, making matching more reliable.&lt;BR /&gt;- In the SupportInfo, you can search vf_agent_srv.trace for that username to see if any errors appear.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;D) The desired policy has definition properties that do not match.&lt;BR /&gt;- Get the details of the app or file by browsing to it using windows explorer.&amp;nbsp; Then right click &amp;gt; properties &amp;gt; EPM tab.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;- in vf_policies., find the desired policy.&amp;nbsp; Then find ApplicationGroup id&lt;BR /&gt;- Copy that application group ID.&amp;nbsp; Then search downwards for that ID to find the definitions that are in the policy.&amp;nbsp; Look through each definition's properties (file name, publisher, location, product, etc) to see if they match what is shown on the EPM tab&lt;BR /&gt;- Note you could also just compare policies in the EPM console, since it is easier to read than looking through xml.&amp;nbsp; The benefit to just looking at the xml is you know that these are the policy settings the endpoint is using..&lt;BR /&gt;&lt;BR /&gt;E) The desired policy has condition settings which do not match.&lt;BR /&gt;- This is rarely used but if your desired policy has a schedule or other condition that doesn't match, it can cause a problem&lt;BR /&gt;&lt;BR /&gt;F) The unwanted policy has exactly the same priority as the desired policy.&lt;BR /&gt;- If two policies have exactly the same priority, they may be chosen at random when the app launches.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;G) The endpoint has not downloaded the desired policy from the EPM SaaS server.&lt;BR /&gt;- If vf_policies.xml contains your policy and all of the expected definitions, this is not the issue.</description>
    <pubDate>Mon, 16 Dec 2024 18:45:27 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2024-12-16T18:45:27Z</dc:date>
    <item>
      <title>EPM - Troubleshoot wrong policy applying</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/epm-troubleshoot-wrong-policy-applying/ta-p/1428375</link>
      <description>The article will provide some steps you can take to troubleshoot why the wrong policy is applying.&lt;BR /&gt;&lt;BR /&gt;Generally, these are the reason another policy is applying instead of your desired policy:&lt;BR /&gt;&lt;BR /&gt;A) The unwanted policy has a higher priority.&lt;BR /&gt;B) The unwanted policy has a definition with child processes enabled and it applies to the parent process.&lt;BR /&gt;C) The desired policy has targeting that does not match.&lt;BR /&gt;D) The desired policy has definition properties that do not match.&lt;BR /&gt;E) The desired policy has condition settings which do not match.&lt;BR /&gt;F) The unwanted policy has exactly the same priority as the desired policy.&lt;BR /&gt;G) The endpoint has not downloaded the desired policy from the EPM SaaS server.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Try to rule out each of the above possible causes until you narrow down the cause,

&lt;H3&gt;Steps&lt;/H3&gt;
A) The unwanted policy has a higher priority.&lt;BR /&gt;- Generate SupportInfo logs.&amp;nbsp;&lt;BR /&gt;-&amp;nbsp;Open the SupportInfo zip and open vf_agent_srv.trace using notepad.&amp;nbsp; Find the PROCSTART event for the process launch and get the name of the unwanted policy which is applying.&lt;BR /&gt;- In the SupportInfo zip&amp;nbsp;look in the trace subfolder.&amp;nbsp; Open vf_policies.xml using a web browser.&amp;nbsp;&lt;BR /&gt;- Search for the name of your desired policy.&amp;nbsp; Then find the "order" of that policy, which is the priority&lt;BR /&gt;- Search for the name of the policy which is actually applying on launch.&amp;nbsp; Check the "order" of that policy.&lt;BR /&gt;- Lower "order" numbers have a higher priority.&amp;nbsp; So you can either confirm that this is the possible cause, or you can rule out this as the cause.&lt;BR /&gt;&lt;BR /&gt;B) The unwanted policy has a definition with child processes enabled and it applies to the parent process.&lt;BR /&gt;- In the SupportInfo zip look at the PROCSTART event for the process launch.&amp;nbsp;&lt;BR /&gt;- If you don't see "Inherited from" you can rule this out as a possible cause&lt;BR /&gt;- If you see "Inherited from", then you need to find the parent process.&amp;nbsp; Look at "Parent=" and take that number.&amp;nbsp; Search backwards until you find a "PID=" number which matches.&amp;nbsp; Check if that PROCSTART process launch says "Inheritable".&amp;nbsp; If it doesn't saw "Inheritable" then keep repeating until you find the reason that the intended policy is not applying.&amp;nbsp; You can then consider if you should have child processes enabled on the policy definition/&lt;BR /&gt;&lt;BR /&gt;C) The desired policy has targeting that does not match.&lt;BR /&gt;- In vf_policies.xml, find the desired policy.&amp;nbsp; Check at the top of that policy's xml to see if there is any user or computer group targeting.&amp;nbsp; It may look like this:&lt;BR /&gt;&amp;lt;UserGroupList&amp;gt;&lt;BR /&gt;&amp;lt;User accountType="User"&amp;gt;Domain\joe.smith&amp;lt;/User&amp;gt;&lt;BR /&gt;&amp;lt;/UserGroupList&amp;gt;&lt;BR /&gt;- check to see if it is matches the user who is launching the app&lt;BR /&gt;- Note in the above example, there is no SID.&amp;nbsp; If you think this could be a possible cause you can use the EPM Admin Utility to add the targeting to the policy.&amp;nbsp; When you do this, it will attach the SID to the policy xml, making matching more reliable.&lt;BR /&gt;- In the SupportInfo, you can search vf_agent_srv.trace for that username to see if any errors appear.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;D) The desired policy has definition properties that do not match.&lt;BR /&gt;- Get the details of the app or file by browsing to it using windows explorer.&amp;nbsp; Then right click &amp;gt; properties &amp;gt; EPM tab.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;- in vf_policies., find the desired policy.&amp;nbsp; Then find ApplicationGroup id&lt;BR /&gt;- Copy that application group ID.&amp;nbsp; Then search downwards for that ID to find the definitions that are in the policy.&amp;nbsp; Look through each definition's properties (file name, publisher, location, product, etc) to see if they match what is shown on the EPM tab&lt;BR /&gt;- Note you could also just compare policies in the EPM console, since it is easier to read than looking through xml.&amp;nbsp; The benefit to just looking at the xml is you know that these are the policy settings the endpoint is using..&lt;BR /&gt;&lt;BR /&gt;E) The desired policy has condition settings which do not match.&lt;BR /&gt;- This is rarely used but if your desired policy has a schedule or other condition that doesn't match, it can cause a problem&lt;BR /&gt;&lt;BR /&gt;F) The unwanted policy has exactly the same priority as the desired policy.&lt;BR /&gt;- If two policies have exactly the same priority, they may be chosen at random when the app launches.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;G) The endpoint has not downloaded the desired policy from the EPM SaaS server.&lt;BR /&gt;- If vf_policies.xml contains your policy and all of the expected definitions, this is not the issue.</description>
      <pubDate>Mon, 16 Dec 2024 18:45:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/epm-troubleshoot-wrong-policy-applying/ta-p/1428375</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-12-16T18:45:27Z</dc:date>
    </item>
  </channel>
</rss>

