Our software guys using SEP 11.6 are complaining that our policy scheduled scans are causing massive disk access. Not the cpu, disk access. The end result is they can take 2 minutes or more to open one single file. Since they are programming software all day, 2 minutes for each file is making them very unhappy with performance.
Problems /questions are:
1. I can reschedule the scan, but: If I go for 5 pm if they don't scan then I believe it kicks in the next day at 8 (also bad)
2. I don't see a way to lower the intensity of the scan. I have plenty of files excluded, (c files things like that since they are plain text) does scheduled scan use the exclusion list.
3. These guys are responsible enough to run their own scans. I get almost no virus incursions since if one of them gets a browser pop up saying "you have a virus" they immediately bring up task mgr and kill the browser process and then scan. (engineers,they tend to be a bit detail oriented) :)
4. I can unlock the policy setting, but that impacts others outside of our branch that might not be as responsible.
I do wish the product could detect the last full scan and if it was within a time window just ignore the scheduled scan. i.e. if the scheduled scan's on Wednesday and the user manually did a full scan on Tuesday that would trigger an exclusion on the scheduled scan. (I don't believe that feature exists...:( )
Any suggestions: My software engineers are very unhappy with their performnce degrading so much during the scheduled scans.