am:
> some people have had problems with this
OK
> but in general it does work
You use the most peculiar logic. I have _multiple_ computers where it does not work correctly. Others have the same problem also. I just can't figure out where you're going with this. Whether you're apologizing for Symantec or if you're dismissing the problem. I just can't figure out what you're actually trying to say.
Here's the logic.
1. The standard dictionary definition of "idle" is "not working or active; doing nothing; not in use or operation."
That's not my definition, that's the dictionary guru's definition. But I agree with it. It's just COMMON SENSE.
2. NIS 2010 will run an "idle" (sic) scan when the cpu is 100% busy. That's an absolute fact, not an unfounded belief, rumor, or assumption. Multiple customers. Multiple computers. Multiple OS's.
3. But NIS 2010 will _not_ run an idle scan when the cpu is 0% busy -- if the mouse is touched. Go figure.
Conclusion: (well, _one_ conclusion) Symantec does not use the common definition of the word idle. The one that makes sense.
Why does this matter? Because when you start up a LONG RUNNING process and walk away, you expect it to finish in a certain amount of time. So when you return and see that it's not completed -- but there is an "Idle scan" pop-up on the screen -- you're really disappointed.
> I've tested it quite a bit at different times.
Test some more. _Multiple computers_. Multiple OS's (xp, vista, 7). Mbam and MS malicious software removal tool full scans. I've even had an idle scan launch during a lengthy windows update! Video conversion, compile code -- anything where neither the keyboard nor the mouse are touched.
> If something else is running in the background during a NIS Idle scan,
> this does not interfere with the use of the computer.
I'm not sure what to make of this statement.
I'm uncertain whether non sequiter or oxymoron best applies.
Let's parse your words. First half.
"If something else is running in the background during a NIS Idle scan"
"Something else" does not run "in the background" during an "NIS idle scan". You have worded it exactly backwards!
An "NIS _idle_ scan", unfortunately, does run "in the background" while "something else" IMPORTANT that the customer started is running in the foreground.
If an "NIS idle scan" is running at the same time as a more important _foreground_ process, then it is not (wait for it) "an IDLE scan"! You can call it whatever you want -- a whenever-the-computer-is-busy scan -- but it's clearly not an idle scan.
Parse the second half.
"this does not interfere with the use of the computer."
This statement indicates a complete lack of understanding of the problem.
The computer belongs to its owner, in this case a Symantec customer.
When the owner starts a LONG RUNNING PROCESS, he relies on Symantec to keep their word. In this specific instance, it means not starting an IDLE scan while that customer is running something important that is using, say, 100% of the cpu. For an important, long running process.
If Symantec starts a while-the-computer-is-100%-busy scan (and perversely calls it an "idle" scan), then Symantec is usurping the computer from its rightful owner. And greatly lessening the value of their product to their customers.
Not sure what you mean by manually running a full Idle system scan though. You can run a full manual system scan but you cannot force an IDLE full system scan. 
