My freshly installed Windows Server 2012 installation with Forefront Endpoint Protection (FEP) installed just wouldn’t update.Googling the error message gave me a lot of ‘you’re infected’ posts.And in the end (again) it’s just a stupid button you have to click.
Error code: 0x80070490 Error description: Forefront Endpoint Protection couldn’t install the definition updates. In the eventlog you will see the following nothing saying message: Microsoft Antimalware has encountered an error trying to update signatures.
New Signature Version: Previous Signature Version: 1.143.1680.0 Update Source: Microsoft Update Server Update Stage: Search Source Path: Type: Anti Virus Update Type: Full User: NT AUTHORITY\SYSTEM Current Engine Version: Previous Engine Version: 1.1.9103.0 Error code: 0x80248014 Error description: An unexpected problem occurred while checking for updates.
For information on installing or troubleshooting updates, see Help and Support. 😯 Well it’s just Microsoft disabling updates for all other Microsoft products except Windows by default.
The Windows Update Log will say the following: – RESUMED — COMAPI: Search [Client Id = Microsoft Forefront Endpoint Protection (1F383481-F70E-4E7A-8B69-C4B4A23928E3)] – Updates found = 0 – WARNING: Exit code = 0x00000000, Result code = 0x80248014 ——— — END — COMAPI: Search [Client Id = Microsoft Forefront Endpoint Protection (1F383481-F70E-4E7A-8B69-C4B4A23928E3)] ————- WARNING: Operation failed due to earlier error, hr=80248014 FATAL: Unable to complete asynchronous search. What you need to to solve it: Open up your windows update screen.
You will see directely what your causes your error. Click find out more In the browser that opens check I agree and click Install Now Windows Update will download updates for ‘other Microsoft Products’ as well. FEP will update like a charm How to fix this on Windows 2008/2008R2/2012/2012R2 Server Core Update: I’m playing around with Server Core a little at the moment.
In an enterprise environment using Microsoft Forefront Client Security (FCS), it is important to be able to quickly and easily deploy antimalware (antivirus and antispyware) definition updates throughout the organization.
FCS accomplishes this by leveraging Windows Server Update Services (WSUS), which is also leveraged by Microsoft System Center Configuration Manager 2007.
While FCS makes use of the WSUS engine in order to deploy definition updates to all of the clients FCS manages, System Center Configuration Manager uses WSUS to provide metadata to the scanning engine on Configuration Manager clients that facilitate software updates.
When customers already have a System Center Configuration Manager infrastructure in place, FCS must use that same WSUS infrastructure, as the local Windows Update Agent can only be assigned to a single WSUS server.
This means that the WSUS infrastructure will be a shared resource for both FCS and Configuration Manager.
This document provides guidance on how to configure FCS definition updates to use an existing Configuration Manager WSUS infrastructure while ensuring that both Configuration Manager and FCS function properly and work together in harmony.