Fep definition status not updating

Posted by / 24-Sep-2016 21:47

Fep definition status not updating

You will need to remove any group policies that may have been configured to disable Windows Defender on domain machines.

I created a separate Windows 10 SCEP policy and deployed it against my collection of Windows 10 machines, whereupon I applied a SCEP 2012 standard desktop policy, modified to include Outlook 2010/2013 exclusions.

In previous OS versions the anti-virus client was replaced by System Center Endpoint Protection (SCEP) software when it was managed by SCCM.

The Authentic Users group only gets read permissions, not start/stop permissions as I feared, so I’m fine with that.

I just left out the Power Users group as it’s not used in our environment.

FEP was built on Configuration Manager 2007 (R2 and R3 supported), so anyone with Configuration Manager deployed now has the unique ability to deliver desktop security on your existing infrastructure.

That means you’ll have: – A single console to manage health and protection of user systems – One server infrastructure to maintain – A single mechanism to deploy software and updates to clients – Central policy implementation for security and management – A single solution that desktop administrators need to be trained on, regardless of role As an added plus, FEP will even detect and remove the most common client antimalware agents currently residing on your current systems to streamline deployment.

fep definition status not updating-73fep definition status not updating-33fep definition status not updating-21

Both of my VMs were not previously managed and it took until a reboot for them to actually report into the console as managed.

One thought on “fep definition status not updating”