In the console, I have a scan job setup to scan each morning at 3am with a duration of 2 hours. The targeted computers that are turned on when the scan initiates scan normally, as expected.
The targeted computers which are turned off obviously do not scan, as expected. However, the problem is that the next time a computer which missed a scheduled scan due to being turned off, is turned on, it starts to scan immediately. Sometimes (for example if a user has been on vacation for a week) there will actually be multiple scans jobs running concurrently on the machine as soon as it is turned on. For example a “Full Scan” and a “Quick Scan” job will be running at the same time.
The scans slow the computers down which is why we run them at night. As I mentioned before, I set the duration for each scan job to two hours. My desire is to have any computer that miss the scan, not scan again until the next scheduled job it is turned on for.
What I did was configure group policy to remove the shutdown button from the start menu. I have avast! configured to shut computers down at night after the scans. You will have to tell your users not to log off from the login screen though.
+1 Bump- Yes please! This is the behaviour we want also. Scanning when the pc is switched on is too draconian. Especially if it happens to the business owner/CEO who wants to do some work right now without being slowed down/interrupted by a scan.
A proposed solution would be similar to the Windows Update dialog- Tell the user the scan was missed because they turned off their pc, and emphasizing the risk/importance of doing scans- BUT with a option to either run now, postpone or dismiss would be more appropriate in a corporate workplace.
I did as Paul suggested and it didn’t work. With PerformActionOnStartup set to zero, the missed scan still ran as soon as the targeted machine booted up. Can someone from Avast PLEASE address this issue? This is becoming a huge problem. As an example, our office was closed on Monday for the holiday and when everyone came in on Tuesday morning and turned on their computers, I was suddenly inundated with complaints about slowness. This was due to a missed scan which had been scheduled to run on Monday night running as soon as the computers were turned on.
To make things worse, the client is password-protected and so the only way to stop the scan from running on 25 machines is for me to remote into each machine one at a time and manually stop the scan. There doesn’t appear to be a way to cancel a scan from the console like you could from the old ADNM.
“Avast start scanning after a missed job”, its not a bug its a feature
I know this problem since we installed the bpp in September and i get no “good” answer to solve this problem. Before, we had avira antivir and there was an option to cancel missed jobs. I think it will be solved after the release of the “new” admin console in january like avast 4.8.
→ the only way is to log in the admin console and end all running scans, so you have not to log in every machine…
