That in turn would bring up a window showing lots of useful information including the name of the applied antimalware policy (if any) as per the screenshot below: In System Center 2012 Configuration Manager RTM if you deployed SCEP to a computer and wanted to quickly verify what policy had been applied to that computer you could open the SCEP client UI on the client computer, click on the downward pointing arro w beside help and select the option About System Center Endpoint Protection. To demonstrate the change, and what it can mean for you when troubleshooting, we need to have a quick history lesson. This change is good because it allows clients to merge settings from multiple antimalware policies however the side-effect of this change means troubleshooting which AntiMalware policy is applied to the client is harder to determine.
This means that if more than one antimalware policy is targeted to collections that the computer is a member of, then those policies will be merged together and the highest priority options within those policies are used. Client-side merge also honors the priority that you configured for each antimalware policy. Some settings are also merged, such as exclusion lists from separate antimalware policies. When two settings are in conflict, the highest priority option is used. Multiple antimalware policies that are deployed to the same client computer are merged on the client. A new functionality called Client Side Merge is included with SP1. One of the many changes in System Center 2012 Configuration Manager Service Pack 1 is related to the way the System Center Endpoint Protection (SCEP) client processes anti malware policy.
0 kommentar(er)
