Just a quick heads up on a KB article we just published. This one talks about an issue where attempting to export an Antimalware policy in System Center 2012 Endpoint Protection 2012 (SCEP) fails with the error:
The specified settings failed to be exported!
In this case, the error occurred because the policy had an ampersand character (&) in the name but other characters such as ", ', < and > can cause it as well. You can read the entire article here:
2784157 - Attempting to export a Malware Policy in Endpoint Protection fails with "Specified Settings Failed to be Exported" (http://support.microsoft.com/kb/2784157)
J.C. Hornbeck | Knowledge Engineer | 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/
App-V Team blog: http://blogs.technet.com/appv/ MED-V Team blog: http://blogs.technet.com/medv/ Server App-V Team blog: http://blogs.technet.com/b/serverappv
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/
Here’s a KB we just published that talks about a condition where the status displayed in the FCS Malware Summary report may be a little bit confusing:
=====
When viewing the Forefront Client Security (FCS) Malware Summary, it may not contain any data and instead simply report "There is no relevant information."
This occurs if no malware has been detected in the last 24 hours. This is by design.
When there is no malware that has been reported in the last 24 hours, the Malware Summary will not show a graph for 0. Instead it will say "There is no relevant information" as mentioned above.
For the most current version of this article please see the following:
2787508 - Forefront Client Security Malware Summary reports "There is no relevant information"
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security 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/