The article will provide some steps you can take to troubleshoot why the wrong policy is applying.
Generally, these are the reason another policy is applying instead of your desired policy:
A) The unwanted policy has a higher priority.
B) The unwanted policy has a definition with child processes enabled and it applies to the parent process.
C) The desired policy has targeting that does not match.
D) The desired policy has definition properties that do not match.
E) The desired policy has condition settings which do not match.
F) The unwanted policy has exactly the same priority as the desired policy.
G) The endpoint has not downloaded the desired policy from the EPM SaaS server.
Try to rule out each of the above possible causes until you narrow down the cause,
Steps
A) The unwanted policy has a higher priority.
- Generate SupportInfo logs.
- Open the SupportInfo zip and open vf_agent_srv.trace using notepad. Find the PROCSTART event for the process launch and get the name of the unwanted policy which is applying.
- In the SupportInfo zip look in the trace subfolder. Open vf_policies.xml using a web browser.
- Search for the name of your desired policy. Then find the "order" of that policy, which is the priority
- Search for the name of the policy which is actually applying on launch. Check the "order" of that policy.
- Lower "order" numbers have a higher priority. So you can either confirm that this is the possible cause, or you can rule out this as the cause.
B) The unwanted policy has a definition with child processes enabled and it applies to the parent process.
- In the SupportInfo zip look at the PROCSTART event for the process launch.
- If you don't see "Inherited from" you can rule this out as a possible cause
- If you see "Inherited from", then you need to find the parent process. Look at "Parent=" and take that number. Search backwards until you find a "PID=" number which matches. Check if that PROCSTART process launch says "Inheritable". If it doesn't saw "Inheritable" then keep repeating until you find the reason that the intended policy is not applying. You can then consider if you should have child processes enabled on the policy definition/
C) The desired policy has targeting that does not match.
- In vf_policies.xml, find the desired policy. Check at the top of that policy's xml to see if there is any user or computer group targeting. It may look like this:
<UserGroupList>
<User accountType="User">Domain\joe.smith</User>
</UserGroupList>
- check to see if it is matches the user who is launching the app
- Note in the above example, there is no SID. If you think this could be a possible cause you can use the EPM Admin Utility to add the targeting to the policy. When you do this, it will attach the SID to the policy xml, making matching more reliable.
- In the SupportInfo, you can search vf_agent_srv.trace for that username to see if any errors appear.
D) The desired policy has definition properties that do not match.
- Get the details of the app or file by browsing to it using windows explorer. Then right click > properties > EPM tab.
- in vf_policies., find the desired policy. Then find ApplicationGroup id
- Copy that application group ID. Then search downwards for that ID to find the definitions that are in the policy. Look through each definition's properties (file name, publisher, location, product, etc) to see if they match what is shown on the EPM tab
- Note you could also just compare policies in the EPM console, since it is easier to read than looking through xml. The benefit to just looking at the xml is you know that these are the policy settings the endpoint is using..
E) The desired policy has condition settings which do not match.
- This is rarely used but if your desired policy has a schedule or other condition that doesn't match, it can cause a problem
F) The unwanted policy has exactly the same priority as the desired policy.
- If two policies have exactly the same priority, they may be chosen at random when the app launches.
G) The endpoint has not downloaded the desired policy from the EPM SaaS server.
- If vf_policies.xml contains your policy and all of the expected definitions, this is not the issue.