Hi,
TECHNICAL ARTICLE:
HOW TO INSTALL AND CONFIGURE FOREFRONT END POINT PROTECTION ROLE FOR SYSTEM CENTER CONFIGURATION 2007 !!!
What's Forefront Endpoint Protection 2010 for System Center Configuration Manager?:
Forefront Endpoint Protection 2010 (FEP), the next version of Forefront Client Security, enables businesses to simplify and improve endpoint protection while greatly reducing infrastructure costs. It builds on System Center Configuration Manager 2007 R2 and R3, and allows customers to use their existing client management infrastructure to deploy and maintain endpoint protection.
What’s New in Forefront Endpoint Protection 2010?:
Usage Scenarios for Forefront Endpoint Protection 2010:
Let's GO! 
for the requirements!
What's in this post?:
In this post, i explain how to install and configure Forefront EndPoint Protection ROLE for System Center Configuration Manager...
Before starting, it is necessary to download the Forefront EndPoint Protection sources available HERE
Related FEP Resources
Let's GO! for the FEP installation!
I have take in my example:
1 Domain controller Acttive Directory (installation not detailed in this post)
1 SCCM Server (installation not detailed in this post)
1 Workstation Windows 7 Professional (installation not detailed in this post)
Have administrators Right lol
Have Forefront End Point Protection Sources accessible through links at the top
In first time and after install SQL server and SCCM (not detailed in this post), you do follow this KB Microsoft (KB2271736):
Example under:
In Microsoft System Center Configuration Manager 2007, the ManagementClass class for Windows Management Instrumentation (WMI) is defined in the Managementclassdescriptions.xml file. This .xml file is in the following path:
<Drive>:\Program Files (x86)\Microsoft Configuration Manager\AdminUI\XmlStorage\ConsoleRoot
However, this .xml file cannot be changed and is not extendable.
After you install this hotfix package, you can add more ManagementClass classes for WMI. To do this, follow these steps:
1. Create a folder named ManagementClasses in the following path:
<Drive>:\Program Files (x86)\Microsoft Configuration Manager\AdminUI\XmlStorage\Extensions
2. Create an .xml file that has the ManagementClassDescription data type and that defines any added ManagementClass classes.
3. Add the .xml file to the ManagementClasses folder.
Folder ManagementClasses dedicated to FEP install :
After FEP installation you see that the FEP files product content added a lot of XML files.
We can Begin installing FEP 2010, launch the setup
Select language (English in my post) and click FEP 2010
Enter the Name and Organization Name and click Next
Select Accept licence terms... and click Next
Select Advanced topology option and click Next
Select three options and click Next
Click Next
Indicate the:
URL: specify the FQDN of the server is preferable if you have an infrastructure with multiple Active Directory domain forest
UserName:Attention, not to use the domain admin account (forjust an example) but rather a dedicated account, with access to the database SQL Reporting Services server.
Password: Indicate the account password
Click Next
if you do not follow the recommendations, a message appears telling you the problem.
After setting the parameters correctly, continue installation by clicking Next
Select yes or not on the update option and the Customer Experience improvement Program to communicate information to Microsoft... and Click Next
Select Join Microsoft Spynet / Basic Spynet membership on the Microsoft Spynet Policy Configuration tab and Click Next
Information on Microsoft Spynet Policy Configuration option:
This information helps Microsoft create new definitions for improved protection, which can help your software better detect and notify you of potential malware. Basic Membership enables the Dynamic Signature Service to provide updates based on behavior monitoring without waiting for the regular signature update process
Click Next
Click Next
Click Install
Click Next
Click Finish
After installing FEP, a new container Microsoft Endpoint Protection is added to the SCCM console, enjoying interface
Several collections have also been created to manage Front End Point Protection 2010..., I'll tell you a little more in my next posts
Several packages have also been created to deploy and manage Front End Point Protection 2010 client by SCCM..., I'll tell you a little more in my next posts
Here is an example of the SCCM/FEP reports available after installation, pretty not?
Who's thanks, thanks to SQL Reporting Services
FEP client interface module was inspired by Windows Defender and replace it when installing the FEP client or when installing the standalone Microsoft security solution for specific Microsoft Security Essentials.
Note: When you install the FEP client package, it will automatically uninstall existing antimalware clients, including:
Forefront Client Security version 1, including the Operations Manager agent
Symantec Endpoint Protection version 11
TrendMicro OfficeScan version 8.0 and version 10.0
McAfee VirusScan Enterprise version 8.5 and version 8.7
Symantec Endpoint Protection Small Business Edition version 12
Symantec Corporate Edition version 10
FEP adventure is launched soon for new posts
Bye
Michaël BERTUIT