I have a server (Windows Server 2012 R2) with 3 large hard drives (in total about 1.5TB of data), and a policy that runs a full scan every week. The scan predictably never finishes, as it is taking 24 hours+ and then locking up, and the policy is not ideal for this particular server.
I have put this server into a separate group that does not inherit the scan policy and has no administrator-defined scans via SEPM. It appears that you cannot customize a SEPM defined scan to only run on one specific drive, only preset folders for some reason.
So instead, from the local agent I defined 3 scans, one for each drive that happen on different nights, so as to the split up the workload.
However, when I went to check the logs, none of the locally-defined scans have run. If I have to execute these manually every week it defeats the purpose of a schedule.
How can I troubleshoot this? Are locally-defined scans overridden on managed clients?
