Not sure if this is for ePO or on the client side. What we have is a file we run on startup on each PC that we have added to the exclusion list. I have verified it is in the policy of each PC but it still gets tagged by AccessProtection. I got a screenshot of the right windows and the accessprotection log showing it caught it even though it is in the exception list for the correct group. I also have the samething happening with a file in the system32 folder. It is in the exceprtion list and still gets caught by our ondemand scan every 14 days. I have restarted many times as well as wake up the agent.
I need to know why it is still be caught as it is been added as an exception. Is it a bug? What did I miss?
lol, never mind, I apparently can't read. I have included the file now, it was win7McAfee88test.