System center 2016 endpoint protection clients not updating potassium argon is a radiometric dating method that involves
Hi, a question on SCEP on server 2016 (full desktop experience). the scep console is also not installed on server 2016.
Is it true that windows defender stays installed when SCEP is installed? Under installed programs, in control panel, SCEP shows as installed, 0 MB in size.
Both errors 0x80248014 and 0x8024402c had occurred when someone tried to manually update the definitions using the GUI.
After a little research and thanks to the Forefront Endpoint Protection Blog I had found that both of these errors had the same core cause.
Is this correct or was SCEP not installed correctly on the server 2016 computer?
I'm guessing it's like Windows 10; there's no Agent installed, it just uses the baked in Windows Defender, and uses the SCEP client to manage exclusions/settings via SCCM policy.
In this clients case, they have a policy set that doesn’t allow the Windows Update clients to go to Microsoft Updates. Which brings us to the third issue we had to resolve.
I am going to start with the issues my client was having when manually trying to update the definitions by using the GUI and then go into why the client wasn’t getting updates from Config Mgr.
I will give you a high level reason why at this client they where getting these errors.
Updating the antimalware definitions in FEP/SCEP fails with error 0x80248014.
If someone uses the GUI and manually tries to update the client, that process uses the Windows Update client.
When the endpoint client updates via Config Mgr it using the Software update component piece of the Config Mgr Client.