Forefront not updating from sccm

var microsoft = microsoft || ; = || ; = (function(){ return { "click Tale Configuration": , "Internal Content Config": , "Mwf Configuration": , "Rps Sign In Info": , "Products Service Config": , "Site Content Config": { "Link Farm Enabled": true, "One Site Service Uri": " the move away from Forefront Client Security to Forefront Endpoint Protection, Microsoft did away with the MOM backend and instead made use of the infrastructure available to System Center Configuration Manager to install, manage and deploy FEP.In spite of the similarities of the underlying infrastructure between SCCM 2007 and SCCM 2012, FEP 2010 does not integrate with SCCM 2012 because one of the installation prerequisites is the presence of the SCCM 2007 administrative console.

The “Basic topology” option installs everything you’ll need for a full FEP environment, including server and console extensions as well as reporting services and reports.Additionally, this installation makes use of the existing SCCM environment to target the right servers (eg: SQL server).There may be times when you would want to target different SQL servers or perform a fully customised installation, but for our lab purposes the “Basic topology” option is sufficient.Next, make sure that the SQL Reporting Server URL is correct, and select an account with sufficient access to run reports.

In the lab environment I used a domain admin account which isn’t recommended in an enterprise environment.

Caption: FEP 2012 Installation – SQL report execution account It’s worth ensuring that the system is using Windows Update to automatically keep FEP 2012 up-to-date (the FEP 2012 client will also be installed on the system as part of the installation) and joining the Customer Experience Improvement Program (CEIP) is always worth it – Microsoft does actually receive the information and uses the metrics to improve current and future products.