![system center endpoint protection 2012 sp1 system center endpoint protection 2012 sp1](https://4sysops.com/wp-content/uploads/2012/06/System-Center-Endpoint-Protection-Antimalware-Policy.png)
![system center endpoint protection 2012 sp1 system center endpoint protection 2012 sp1](https://s4.51cto.com/attachment/201306/27/401810_1372346934ABNL.jpg)
Method 2: Command-line Windows Registry query
#System center endpoint protection 2012 sp1 how to
This is because this policy has the highest priority among the other two policies causing its settings to be merged with the others. Today I want to talk about how to troubleshoot System Center Endpoint Protection (SCEP) anti-malware policies on your client PCs. In the screenshot below, you can see that “SWS EP VIP Policy” has all its settings merged into the other two policies.
![system center endpoint protection 2012 sp1 system center endpoint protection 2012 sp1](https://sccmentor.files.wordpress.com/2014/08/sceptrigger02.jpg)
Basically, if multiple anti-malware policies are targeted to the same collection, the policy with the highest priority wins when there are conflicting settings.įor a quick overview of which policies are being applied, you can open the log at C:\Windows\CCM\Logs\EndpointProtectionAgent.log or you can open the SCEP client, click on the drop down arrow next to the “Help” menu and choose “About”. Since the introduction of SCCM 2012 SP1, a new feature called “Client Side Merge” was introduced. System Center Security Monitoring Pack for Endpoint Protection now supports System Center 2012 Operations Manager SP1. Today I want to talk about how to troubleshoot System Center Endpoint Protection (SCEP) anti-malware policies on your client PCs.