I would say those files are in the scan cache and have not changed.
To see this in action On-Demand Scan a subfolder (so it does not take long) and examine the onDemandScan_Activity.log - note the stats:
Files not scanned:
Now scan the same folder again and check the new stats in the log. Almost all those files will not be scanned. If you open/close or change a bunch of those files and ODS again you'll see Files Scanned increase and so on.
ENS has intelligent ODS and will not scan files if they've not changed since the last ODS.
I thought that too, and sorry for not mentioning in my first message, but looking at the policy I can see that the cache is disabled. Can you think of some other reason for this? If indeed the scan was stopped before it could scan all files, it would show in the logs simply as "files not scanned"?
I have a question for you regarding something related.
ENS 10.5 will scan files unmodified with a new AMCORE /DAT file etc?
ex: today i scan a file with an AMcore, if after 3 days i will scan again the same file (unmodified), will it be scanned or not?
eduardo0407 I'm having a look in my own OnDemandScan_Activity.log, and I see what you mean. For my full scan, I see 1,300,000 files scanned, and 110,000 files not scanned. My scan is limited to 12 hours, and took 189 hours to complete (I'm doing initial testing around how long it'd take to scan a system, so my scans aren't properly configured yet). So even though it *is* limited by time, it still ran to completion, but didn't scan almost 10% of them. Once I get my policies set up properly, if it's still happening, I'll probably log a ticket for it. I'd suggest you do the same in the meantime.
jabii If you have a question, start your own thread for it, don't try to hijack someone else's question. It just confuses things and makes helping both of you more difficult.