Freigeben über


Introducing Forefront Endpoint Protection 2010

From Ariel Katz, Director of Program Management:

I am pleased to announce that Forefront Endpoint Protection 2010 Beta is publicly available for everyone to download.

FEP, the next generation release of Forefront Client Security, will simplify and improve endpoint protection while greatly reducing infrastructure costs. It builds on System Center Configuration Manager 2007 R2, enabling you to use the existing client management infrastructure to deploy and manage endpoint protection.  This shared infrastructure lowers ownership costs while providing improved visibility and control over endpoint management and security.

Key new features that you will be able to evaluate in this beta release are:

  • Integration with Configuration Manager -  Single interface for managing and securing endpoints reduces complexity and improves troubleshooting and reporting insights.

  • New Antivirus Engine -  Highly accurate and efficient threat detection protects against the latest malware and rootkits with low false positive rate.  

  • New behavioral threat detection -  Protection against “unknown” or “zero day” threats provided through behavior monitoring, emulation, and dynamic translation.

  • Dynamic Cloud Updates: On-demand signature updates from the cloud for suspicious files and previously unknown malware

  • Windows Firewall management -  Ensures Windows Firewall is active and working properly on all endpoints, and allows administrators to more easily manage firewall protections across the enterprise.

The download is available now on our download center (https://www.microsoft.com/downloads/details.aspx?FamilyID=8b46c3ff-d9a0-4741-8ba5-458c1b3d2257) and I invite you to install and test in your environment today. We look forward to hearing what you think. 

Ariel Katz, Director of Program Management

Comments

  • Anonymous
    January 01, 2003
    Hello, This prerelease version of FEP 2010 can be installed on a Configuration Manager site server that is using either SQL Server Standard Edition or SQL Server Enterprise Edition. For more information on the requirements for Configuration Manager R2, see SQL Server Site Database Configurations here: technet.microsoft.com/.../ee344146.aspx For the FEP 2010 beta documentation, including the release notes, see technet.microsoft.com/.../ff823816.aspx Thanks!

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    Hello folks, Please direct your product questions over to the support forum for FEP: social.technet.microsoft.com/.../threads Thanks!

  • Anonymous
    January 01, 2003
    As a non-SCCM customer, does MS suggest we must now license SCCM for all our users, in addition to FEP, or will there be some sort of FEP/SCCM bundle for non-SCCM customers?  Or, will FEP grant some sort of limited-use license for SCCM?  I look forward to this question hopefully being answered here or in the forthcoming TechNet webcast next week. Thank you.

  • Anonymous
    July 20, 2010
    SQL Standard is not supported? Only Enterprise? Ouch!

  • Anonymous
    July 20, 2010
    Are any readme.txt or release notes files on how to install from evalcdmedia_en_US_x86.zip are available with FEP 2010 Beta?

  • Anonymous
    July 23, 2010
    Is there a way to enable the Network Inspection Signatures?

  • Anonymous
    July 25, 2010
    Will this product work with SCCM vNext? I would hate to get too involved with the new product only to find out that it won't work with this one.

  • Anonymous
    July 27, 2010
    Where is the documentation on how to get updates to FEP clients in a SCCM integrated environment? The process for FCS wasn't very good and I was hoping to see some improvement in FEP.

  • Anonymous
    July 30, 2010
    The comment has been removed

  • Anonymous
    July 30, 2010
    The comment has been removed

  • Anonymous
    July 30, 2010
    @Anonymous - "Endpoint Protection" as a concept has been around longer than Symantec's product.  It's no different than someone picking "AntiVirus" as a name for their product.