This article describes an anti-malware platform update package for the following clients:
- Microsoft System Center 2012 R2 Configuration Manager Endpoint Protection clients
- Microsoft System Center 2012 Configuration Manager Endpoint Protection Service Pack 1 (SP1) clients
- Microsoft Forefront Endpoint Protection 2010 clients.
These packages update Endpoint Protection client services, drivers, and UI components. Microsoft regularly releases anti-malware platform updates to guarantee consistency in protection, performance, robustness, and usability in a malware landscape that is constantly changing. This update package is dated November 2013.
For additional details and a link to the update, please see the following:
KB2907566 - November 2013 anti-malware platform update for Endpoint Protection clients (http://support.microsoft.com/kb/2907566)
J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division
Get the latest System Center news on Facebook and Twitter:
System Center All Up: http://blogs.technet.com/b/systemcenter/ System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/ System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/ System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Windows Intune: http://blogs.technet.com/b/windowsintune/ WSUS Support Team blog: http://blogs.technet.com/sus/ The AD RMS blog: http://blogs.technet.com/b/rmssupp/
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
This update is triggering a reboot needed message on our servers and computers despite our policies are against that, and even a couple of servers have been reebooted by ccmexec. Any guidance on avoiding that will be much apreciated, thanks a lot.