So, this is one of the odd ones.
We have setup our SCCM/SCEP to send e-mails when new malware are found in selected collections (Alerts).
During last week, I was surprised to see that our environment was without malware at all (according to the endpoint protection status in the SCCM console) . That's very unlikely to happen, so I started to go about test the SCEP client on a newly installed
W81 machine. I did a few test with the following
http://www.eicar.org/86-0-Intended-use.html
SCEP instantly found the string as malware, which is what I hoped for. I waited to see if the client would report that back to SCCM as usually, but no. Nothing ever shows up in the console.
Long story short; we went back to see when the last time we ever recieved an e-mail based on a malware-alert in SCCM. The last e-mail was dated march 14th 2015.
So we went back to see what happened on our clients back in march, and during our troubleshooting we went through every software update we released in march, and it appears thatKB3025417 is causing the trouble here. (Note: I also suspect that the update itself is unnecessary given we have SCEP, and the update is related to windows defender. However, the update is seen as required by all W81 clients)
We ended up excluding the mentioned update, and reinstalled a client and voila; SCEP works fine again. The minute we install the update, SCEP on the client is no longer reporting the found malware back to SCCM. Also, uninstalling the update doesn't
do anything. The damage is done.
We found a few other reporting similar behaviour. While they don't mention the KB itself, I suspect it's very same issue:
https://social.technet.microsoft.com/Forums/en-US/34903763-b423-41b4-8783-b75df94337d0/scep-email-alerts-stopped-working-in-sccm-2012-r2?forum=FCSNext
The environment is SCCM 2012 R2 CU4, Antimalware Client Version: 4.8.204.0, Windows 8.1 x64
Also, note that everything around the SCCM client seems healthy. Deployments are installing and reporting back as usual. Nothing else seems broken, and the SCEP component is also healthy.
This is probably a case for MS Support, but given that I see a few others with the same issue, I also suspect that there's alot more out there with the same problem. They just don't know yet, or haven't figured out why it stopped working.
Any pointers or comments to above is much appreciated.
Thanks in advance.
Martin Bengtsson | www.imab.dk