system center endpoint protection 2012 r2

SYSTEM CENTER ENDPOINT PROTECTION 2012 R2 INSTALL
SYSTEM CENTER ENDPOINT PROTECTION 2012 R2 SOFTWARE

You can also export policies that were created in FEP 2010 and import them into SCEP. These templates are generally ready to deploy but can be customized to meet the specific needs of the organization if needed. SCEP also includes several policy templates that provide recommended antimalware configurations for standard workloads. The ConfigMgr administrator enables SCEP in ConfigMgr 2012 by deploying the new Endpoint Protection Point site system role, enabling the Endpoint Protection client, and then configuring the antimalware policies. Because of the tight integration with ConfigMgr 2012, SCEP is easily deployable to environments of any size. The deployment and configuration of SCEP are managed in the ConfigMgr 2012 console. We will expand on these in the remainder of the chapter. Now that we have identified some of the key differences between the FEP 2010 and SCEP products, let’s take a look at some of the additional benefits of the SCEP product.

SYSTEM CENTER ENDPOINT PROTECTION 2012 R2 SOFTWARE

Antimalware software (such as SCEP) is software designed to detect, block, and remove malware. Malware includes items such as computer viruses, worms, Trojan horses, adware, and some rootkits. Some malware attempts to delete files or corrupt the operating system, while others may attempt to steal personal or corporate data. Malware is short for malicious software, which is basically software, code, or scripts that are typically designed to perform invasive, destructive actions on a computer. We will use the term malware a great deal in this chapter, so it’s probably a good idea to define that word.

In ConfigMgr 2012, the role-based security model allows the ConfigMgr administrator to easily delegate the SCEP-related functions to a specific person or group without providing those users with access to other areas of ConfigMgr. Delegating the administration of FEP was a challenge in ConfigMgr 2007.ConfigMgr 2012 has new internal processes that work to greatly reduce the time that elapses between the event and the alerting and reporting. FEP had a delay between when a malware event occurred at a client, such as virus detection, and when that information was made available to the ConfigMgr 2007 administrator.

SYSTEM CENTER ENDPOINT PROTECTION 2012 R2 INSTALL

SCEP includes the endpoint client software as part of the ConfigMgr 2012 client install media, and the SCEP client is enabled and configured in the ConfigMgr 2012 console.

FEP required a separate client to be deployed and installed on each managed computer.

SCEP uses the ConfigMgr site database to store all data.

FEP used two separate databases to store data, FEP_DB and FEP_DW.

Deploy and configure the System Center 2012 Endpoint Protection site system and clientīefore taking a closer look at System Center 2012 Endpoint Protection, let’s take a moment to review some of the key differences between Forefront Endpoint Protection 2010 and System Center 2012 Endpoint Protection:.

As you will see in this chapter, the integration between Endpoint Protection and Configuration Manager is carried forward and greatly enhanced in the System Center 2012 versions of the products. The Forefront Endpoint Protection product has been updated for 2012, and the new version is called System Center 2012 Endpoint Protection (SCEP). Forefront Endpoint Protection (FEP) is Microsoft’s industry-leading security and antimalware product, and the integration with Configuration Manager 2007 allowed administrators to easily manage and control its configuration. System Center Configuration Manager 2007 provided the ability to integrate with Microsoft Forefront Endpoint Protection 2010. Mastering System Center 2012 R2 Configuration Manager (2014) Chapter 15.

System center endpoint protection 2012 r2