NIS 2009: Idle Background jobs all run simultaneously - some cancel themselves

Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.

What you are experiencing is expected behavior-

 

Several of the Norton background task run at a lower priority relative to other tasks (relative to other Norton background tasks, and especially at a lower priority than the Norton real-time protection components) - the Norton Insight Scan and Norton Insight Submission are both in this *lower* category.  

 

Norton Insight Scan, for instance, will run only while the system is in the idle state -  but even when the task has started during an idle period,  Norton Insight Scan (and Norton Insight Submission) will stop prior to completion when the system becomes non-idle. 

 

Coming out of the idle state could be the result of user activity or could be the result of other non-interactive tasks that have placed demands on CPU, I/O, Network or other shared resources. 

 

When Norton Insight Scan is stopped prior to completion because of system activity (when system exits from the idle state), the Background Jobs Status attribute will show a status of cancelled as you indicated.  Your protection is never comprimised as a result of these cancelled tasks, and the cancelled task will be (re)scheduled to run on next idle period, and will be run according to priorities of other tasks that also need to run.

 

I hope this helps.   Please fell free to followup if I have not addressed your concerns or if you have additional questions

 

regards

Roy Fine