Let’s analyze the options to Fix SCCM SCEP Related Issues. In this post, I will try to cover the knowledge acquired from the field to fix different issues of Windows Defender or Endpoint Protection client (a.k.a SCEP?).
Don’t get confused between SCEP and Windows Defender or Endpoint Protection clients. All these are the same from an IT Professional perspective. Microsoft changed the name of SCEP to Windows Defender or Endpoint Protection client.
In this post, I’m sharing the information for Endpoint protection (defender) clients that are managed through Configuration Manager (a.k.a SCCM). Let me know in the comments section if you have any queries/concerns.
Endpoint Protection manages antimalware policies and Windows Firewall security for client computers in our Configuration Manager hierarchy. Till here the statement is absolutely correct and SCEP does what it’s supposed to do but there are cases of offenders who refuse to get the regular definition updates from SCCM and make our entire infrastructure itself vulnerable.
We started this SCEP (Windows Defender or Endpoint Protection client) Remediation project early in 2019 and the task was simple. We just had to make sure all the clients in the infrastructure are running the latest definitions if they are connected to the network.
Sounds simple but when we did our hands dirty and started seeing different errors then we saw limited articles and fixes to help us achieve the goal.
There is not much information available on google too apart from the generic MS article https://docs.microsoft.com/en-us/mem/configmgr/protect/deploy-use/troubleshoot-endpoint-client and the one from Henrik Hoe https://blog.ctglobalservices.com/configuration-manager-sccm/heh/configuration-items-and-baselines-example-scep-client-compliance/
So finally we reached home to HTMD : https://forum.howtomanagedevices.com/ and tried.
Important – Read more about the question here: https://forum.howtomanagedevices.com/endpointmanager/configuration-manager/scep-definitions-not-updating-mecm-2002-adr/
If you are done reading the question then you noticed the HOD – Anoop C Nair Suggested opening case with MS because of the complexity of the question.
Note : Most of the points explained in this blog are from several Microsoft forums and the data was collected from those including several other websites like CTGLOBAL (Link already given in the block above) MANAGE ENGINE, COMPARITECH, BERKELEY, SEARCHSECURITY TECH, TRUSTRADIUS, and REDDIT.
So without further delay let’s deep dive from page 1.
- The evolution of malware
- Overview of System Center Endpoint Protection
- Management + Security
- Overview of the Endpoint Protection client
1. In 1991, 1000 known threats, in 2001 there were 60,000 2. Today there are millions, and it’s growing every day 3. Sophistication and production rates continue to evolve 4. Anybody can do it—full malware suites available online 5. Your stuff is worth money, and they want it!
The below figure shows the current reprehensible entities
Mgmt + Security In Configuration Manager
Infrastructure Changes from FEP 2010
Simplified Deployment of AM Policies
Signature Update Distribution
Simplified Client Setup
Single Interface For Management And Security
Monitoring Client Security
Rich Reporting And Analysis
Management and Real-time Monitoring
Real-time Administrative Actions
Real-time Administrative Actions in Endpoint Protection
Comprehensive Protection Stack
Dynamic Translation With Heuristics
Behavior Monitoring And Dynamic Signatures
Protect Clients With Reduced Complexity
Managing Endpoint Protection client with Command Line Interface – MpCmdRun.exe
Collecting SCEP support logs:
Endpoint Protection Log Files
WMI Namespace and Classes for System Center Endpoint Protection
AntiMalware Health Status
AntiMalware Infection Status
Force State Message for SCEP on SCCM Client
Disclaimer – The information provided on site is for general informational purpose only. All information on the site is provided in good faith, however we make no representation or warranty of any kind, express or implied regarding the accuracy, adequacy, validity, reliability, availability or completeness of any information on website.