The main intension to built System Center 2012 Endpoint Protection on Configuration Manager is to create a single infrastructure for deploying and managing endpoint protection. In previous version (SCCM 2007)System center Endpoint protection was not associated with sytem center configuration manager product. Some of the features that we achived by associating SCEP with configuration manager are mentioned below


1. Central administration for deploying and configuring the Endpoint Protection client.
2. Default antimalware policies can be deployed to groups of computers.
3. Security roles for managing antimalware polices can be managed/controlled
4. Security settings like Windows Firewall changes can be deployed to group of computers
5. Scan and status reports can be genrated easily by configuration manager
6. The endpoint protection client can be updated by monthly patch cycle using SCCM endpoint definition updates
7. Security roles for managing antimalware polices can be managed/controlled
8. Notification can be set via configuration manager for malware compliance computers
9. Scan and status reports can be genrated easily by configuration manager



How to setup and deploy System center Endpoint Protection?



The SCCM 2012 site role responsible for setting up Endpoint protection feature is Endpoint Protection Point . This role should be installed and configured in Central administration site or standalone primary site . In addition to this, Software update point should be configured to deliver definition updates if you want to use Configuration Manager Software updates to deliver definition and engine updates. With this entire prerequisite create client antimalware policy to manage Endpoint protection settings.



Deploying system center Endpoint protection has few steps as mentioned below







Translate

Total Pageviews

Blog Archive

Followers

Linkedin

Popular Posts