Were these machines upgraded from SAV or fresh SEP installs?

I am not sure but I would guess the machines were upgraded from SAV to SEP since we are using SCCM to install software packages.

I had this same issue caused by the SAV to SEP upgrade.

The SAV scan was "stuck" in the registry

It was supposed to be fixed in MP2. Upgrading to MP1 fixed it for me but it sounds like you are on the latest version.

You can call Symantec and get the SymRmvScan utility.

https://www-secure.symantec.com/connect/forums/dou...

Scheduled scans runs more often than is configured in the policy

http://www.symantec.com/business/support/index?pag...

In your scan schedule, do you have the "Randomize scan start time within this period" selected?

If so, whatever your "Scan for up to:xx hours" configuration is, will determine the time window the scan will start within.

i.e. If you schedule your scan for 5pm Monday each week and have the scan alloted to scan for up to 48 hours, the system will initiate the scan anywhere from 5pm Monday to 5pm Wednesday.

Regards,

Chris Bulovic

I have the same problem, but the scan is now scheduled for late night, in the UI is is actually showing as occurring again midmorning. So the problem is not more frequent scans, but the fact that the scan time is not occuring as scheduled.

I do not have the randomization enabled.

Any ideas?

Hello,

  We're experiencing the same problem.  Most of the users are developers who are trying to compile code when the scan kicks off and it absolutely cripples their machines.  This was an upgrade from SAV to SEP and I have tried running the SymRmvScan but it didn't work. 

 We are planning to upgrade to 12 shortly but this is a massive inconvenience.

If anyone has any further ideas on how to mitigate the existing 11 version it would be greatly appreciated as our user community is getting restless and they keep canceling the scans to get their work done.