Endpoint Protection

We are having an issue where certain clients are not running their scheduled scans that are set by the SEPM policies. If you open up the SEP client on the machine the scan schedule shows correct but it is like the scan is failing and shows the next scan time as the next montly. The last scanned time is months past. Anyone have any information on what could be causing this?

Assure that you are having sufficient free space in your OS drive....
If you right click on the scan schedule and click on scan now whether it is scanning?

Check this also
Click Start > Control Panel > gpedit.msc
Go to Windows settings> Security settings > Local policies> User rights assignment.
Edit Adjust Memory Quotas for a Process and Replace a Process Level Token, and add Network Service to the two policies.
Restart the computer after applying the changes.

Is there a GPO assigned to the symantec service, if yes remove that

We are having issues with a couple of users, where the scheduled scan isn't kicking off. Both are fresh installs. I wonder if these security settings are the cause.

Mike

We do not have GPO setup for this domain. If I go to the actually client and kick off a manual scan the scan works fine. Is there a log file that tracks what is happening at time of scheduled scan that I could take a look at?

Hello Dwilson,
you can take a "computers not scan report" from sep manager. and you can see what happend in scan log.
By the way can you send a scan to computers? not scheduled scan. therefore we can test If the rules work client side or not.

Best Regards.
Fatih

I think i have it figured out. What is happening is our scheduled scans are set for 8 pm. Most of our users turn their pc's off when going home (5pm). None of our policy were set to "Retry schedule scan" if the scan failed. This is what I believe to be causing the issue. We are going to adjust our policies accordingly