Microsoft Forefront Endpoint Protection 2010 (beta): Installation Steps

Microsoft Forefront Endpoint Protection 2010~Introduction

Recently it was announced from the Forefront Insurance with implementation of the Beta program of the new antivirus solution for client or server operating system, Forefront Endpoint Protection 2010. Perhaps the most significant change I understand the fact of its operation. The previous version based its functionality as a component of Microsoft Operations Manager 2005. However, in this new version, based on System Center Configuration Manager 2007 for administration, deployment and monitoring. The change not only implies a change in product, but also a change in strategy for managing it. It may be far more appropriate for the concept and treatment through System Center Configuration Manager 2007 from Microsoft Operation Manager 2005 or its successor MS System Center Operation Manager 2007. With this leap in product is passed to a monitoring system to a complete management system. The scope of System Center Configuration Manager 2007 to all systems of an organization makes it more likely to have an agent installed and not the fact deploy SCOM 2007 agent, more oriented towards services and servers.

Installation Requirements

For the installation of Forefront Endpoint Protection 2010 requires the fulfillment of certain prerequisites:

•RAM: 2 GB minimum.
•Disk space: 1GB for service, 6 GB for the database and 6 GB for database reports.
•Operating system Microsoft Windows 2003 SP2 or later.
•No role of the previous version can be installed.
•It must not have any other anti-malware solution.
•Must be running Windows Installer version 3.1 or later.
•Microsoft .Net Framework 3.5. Service Pack 1.
•Microsoft SQL Server 2005 SP2 or 2008 Enterprise with the following components must be installed:
◦Analysis Services.
◦Integration Services.
◦Reporting Services.
◦SQL Server Agent.
•Must submit a site with Microsoft System Center Configuration Manager 2007 SP2 Release 2 with the role of SQL Server Reporting Services configured and installed and configured the following components:
◦hardware inventory.
◦distribution of software.
◦desired configuration management.

Keep in mind that although SCCM 2007 is a pure 32-bit component and can be installed in 64-bit operating systems, there Forefront Endpoint Protection version 32 and 64 bits. You must download and install the version for your operating system on which the server is running SCCM 2007.


Installation Process

The start of the installation is done through a wizard to guide you through the process. It is provided on the front page links to the deployment guides and use of the service agreements.

Once the license accepted the decision of the type of display you want done. This will provide four possibilities:

• Basic topology: All infrastructure will be implemented on a single server.
• Basic Topology database remote report: All except infrastructure reporting system that can be installed on another server.
• Advanced Topology: Defines the procedures for configuring the components of the Microsoft Forefront solution Endpoint Protection 2010.
• Install only the extensions of FEP 2010 for the console of System Center Configuration Manager.

Depending on the type of topology design, following the wizard may vary. In the example shown to over the post, it was decided to use the advanced topology option. In this decision the following options, allows selection capabilities FEP 2010 MS wishing to settle.

• Extension of MS Forefront Endpoint Protection 2010 for System Center: Integrating MS FEP 2010 in SCCM 2007 is done at multiple levels. Integrated into the software distribution procedures and analysis and security configuration through its components. These extensions allow the creation of collections, packages for distribution processes and the creation of objects and baselines used in the desired configuration.
• Service reports and alerts FEP 2010: Allows local installation of components for monitoring MS Forefront Endpoint Protection 2010.
• Installation of extensions EFF console in Configuration Manager 2010 for centralized management.
• 
  
• The next step in the process is to define the parameters of creation of the database. Although the configuration such as packages or libraries will be integrated in the own database of System Center Configuration Manager with regard to management of alerts and threats will be stored in a new database. The server used is the same as that defined in SCCM 2007.
• 
• After that it is time to define the processes of defining the data for the creation of database reports and account and service data for Reporting. For the process to be effective must have completed all the configuration requirements. If it is not so, as shown in the picture below will display a configuration error. To fix it, give permissions to the Network Service (Network Service) on the following file:
  

  C: \ Program Files \ MicrosoftSQLServer \ MSSQL.3 \ ReportingServices \ ReportServer \ rsreportserver.config

  
  The following process of installing MS Forefront Endpoint Protection 2010 is to define the service activation or upgrade to platforms and products and join the improvement program experience.

Within the procedures leading Microsoft for security management, one of them is the creation of SpyNet community. Through this you can be notified and know that others have made on the detection of a potential Malware. Membership allows you to send basic information or advanced improves applications in the fight against malware.

Enter the information sent is the result of the action takes effect, the impact of the threat, locations where lynx and others. The following illustration shows the options to join Microsoft SpyNet.

After the definition of politics SpyNet established, it is time to establish the parameters of the installation.

The last step before starting the installation is to check the prerequisites for installing the service. The following image shows an error and a warning in meeting the prerequisites. The warnings allow the start of the installation process, which did not happen to resolve the errors. Aid showing each warning and error, provides the procedures to be carried out to address them.

After satisfying the requirements of the wizard displays the processes that take place beginning the installation of Microsoft Forefront Endpoint Protection 2010.

Installation Complete

Finished the process, the installation of MS FEP 2010 implies also the configuration of antimalware client on the server automatically. The following image shows the Configuration snap added to the SCCM management console 2007 and the process of updating the antimalware engine in the operating system.