Fep definitions not updating
Event: Client engine terminated due to error This monitor returns the number of events when the Forefront Endpoint Protection client engine has been terminated due to an unexpected error. Try to restart the following two services: Antimalware engine and NIS engine.
If, at any time, Microsoft Forefront Client Security does not update automatically, you will need to update it manually.
Event: Scan encountered error and stopped This monitor returns the number of events when the Forefront Endpoint Protection client scan has encountered an error and stopped. This error record includes the scan ID, type of scan (antivirus, antispyware, antimalware), scan parameters, the user that started the scan, the error code, and a description of the error. If it fails in the same way, look up the error code. Forefront Endpoint Protection can suspend and take routine action on this threat.To schedule the update of the FEP definition package with the latest definitions follow the instructions under the section “How to Use Definition Update Automation Tool with Task Scheduler”.Open your FEP policy and in the Updates tab tick “Use Configuration Manager as the primary source of definition updates” As I configured the FEP updates to be controlled by SCCM, when the FEP client is first installed the icon turns red because the definitions are out of date.I chose a Basic installation as I wanted all components to install on to the SCCM server.I wanted the FEP updates to be controlled by SCCM, so installed this hotfix Next I downloaded the Definition Update Automation Tool for Forefront Endpoint Protection 2010 Update Rollup 1 the instructions at the link above under the section “How to Configure Configuration Manager for Forefront Endpoint Protection Update and Create Deployment Package and Assignment” This creates a Deployment Package and Assignment to install the FEP definition updates.