T06:06:47.173Z Task(Scan -ScheduleJob -RestrictPrivileges -ScanType 2) is scheduled to run in 86400000(ms) from now with period 70114864(ms) T06:06:47.173Z Task(SignatureUpdate -ScheduleJob -RestrictPrivileges) is scheduled to run in 28800000(ms) from now with period 28800000(ms) T06:06:47.173Z Task(Scan -ScheduleJob -RestrictPrivileges) is scheduled to run in 604800000(ms) from now with period 21957080(ms) T06:06:47.173Z Product supports installmode: 0 T06:06:47.173Z AutoPurgeWorker triggered with dwWork=0x3 T05:57:50.420Z Process scan (postsignatureupdatescan) completed. T05:57:40.982Z Process scan (postsignatureupdatescan) started. T05:57:15.492Z IWscASStatus::UpdateStatus() succceeded writing instance with state (1) and up-to-date state(1) T05:57:15.492Z IWscAVStatus::UpdateStatus() succceeded writing instance with state (1) and up-to-date state(1)

In the SCCM console, Active Clients at Risk, the client has Endpoint Protection Enabled showing as Disabled, nothing in the Endpoint Protection Engine Version, nothing for Last Full Scan Start Time, Endpoint Protection Pending Full Scan - No. The AV engine and AV definitions are upto date and the real time monitor is running. Someome did create a new EP policy and pointed the clients at it, but that didn't fix this problem.

We are running SCCM 2012 R2 CU1 on our site system and clients, having upgraded from SCCM 2012 sp1 12 months ago.Ī few of our clients will not run a scheduled scan, even though it displays the Scan date and time in the client properties.

Endpoint protection software run scan