I was referring to setting up a Custom Scheduled Scan. When a user schedules a Custom Scheduled Scan, the Idle Time Scan is turned off by default and an alert box prompts the user about this before exiting the Scheduled Scan dialogue box.
However that "OFF" setting can be changed by the user after the Scheduled Scan has been set up; it is not locked out once a scheduled scan is set.
And in the link that I provided earlier, having an Idle Time Scan run when a Scheduled Scan has already started can cause conflict.
Sorry if I had not made that clear in the previous post.
I just don't understand this objection to leaving Idle Scan alone; when my machine is not being used by me, I'm delighted if this Idle Time is used by Norton productively and that it stops if I come back and even move my mouse.
OK huwyngr,
That's why they are called options or preferences. Because you prefer this (Idle), others prefer Scheduled FSS. Its nice to give users the ability to choose. In this specific instance, Symantec did indeed provided us with these options. Either Idle Full or Scheduled Full Scans.
I don't think you or anybody can ever understand other people's personal preferences.
Btw, leaving aside the Auto gb example (can discuss it another time if you want)..think of color choices...you like blue.. I like black..
OK then. I just set it back to "OFF". (But then how did I get a Scheduled FSS run with Idle set to weekly, after I scheduled the scan? A bit strange..)
By setting it to "Off", will Idle Quick scans still run?...I guess they will. Can you confirn please?
You will be able to get a FSS scan to run with Idle set to Weekly until such time as the FSS and Idle Time Scan both try to run at the same time.
Idle Quick Scans will still run. You can confirm that in your Scan Results History Window.
Are yours still running? I thought you deleted them... Did you rescheduled again? If so, do they run with Idle Scan Option to Off...Well, mine now run with the Idle Scan option to Weekly.
Yep!
In the last 24 hours ... Little Ideas have started to twig in my head - Re : NIS 09
I think I'm finally starting to understand the mysteries of - NIS 09
Fingers Crossed!
Yep ... I have Scheduled another Scan
Nope ... I didn't give a Password
Phil Said...
I was referring to setting up a Custom Scheduled Scan. When a user schedules a Custom Scheduled Scan, the Idle Time Scan is turned off by default and an alert box prompts the user about this before exiting the Scheduled Scan dialogue box.
However that "OFF" setting can be changed by the user after the Scheduled Scan has been set up; it is not locked out once a scheduled scan is set.
And in the link that I provided earlier, having an Idle Time Scan run when a Scheduled Scan has already started can cause conflict.
Sorry if I had not made that clear in the previous post.
Phil Is Correct!
This ability to go back... And turn Idle Scan back - ON ... Is a NIS 09 - Bug!
<< Symantec did indeed provided us with these options. Either Idle Full or Scheduled Full Scans. >>
Either .... but not both set at once which seems to be the "problem" here and elsewhere. Just because options are available it does not mean we have to use them regardless -- I doubt that even Microsoft in their applications have managed to interlock all settings so that there can be no conflict!
<< Symantec did indeed provided us with these options. Either Idle Full or Scheduled Full Scans. >>
Either .... but not both set at once which seems to be the "problem" here and elsewhere. Just because options are available it does not mean we have to use them regardless -- I doubt that even Microsoft in their applications have managed to interlock all settings so that there can be no conflict!
Either .... but not both set at once which seems to be the "problem" here and elsewhere. Just because options are available it does not mean we have to use them regardless -- I doubt that even Microsoft in their applications have managed to interlock all settings so that there can be no conflict!
Please huwyngr..You're a smart guy. I take it that you have understood, that this was not the original problem here. As I have mentioned, when the issue first occured, I had not changed the settings..and the Idle was set to "off"...
OK then. I just set it back to "OFF". (But then how did I get a Scheduled FSS run with Idle set to weekly, after I scheduled the scan? A bit strange..)
When you say "Time Scan Should be left turned off which is the default when you schedule a Full scan", you mean default because we set it to "Off" before we can schedule. Otherwise, we cannot Schedule.
By setting it to "Off", will Idle Quick scans still run?...I guess they will. Can you confirn please?
When you turn Idle Time Scan to OFF, it will not run. This setting is only automatically changed to OFF if a scheduled scan is setup. Not everyone schedules their Full System Scans to run when a system is Idle, and in the interest of letting customers use their preference, this option is not completely blocked. However, an popup window appears when scheduling a Full System Scan regarding this topic. It also makes sense that you wouldn't want both the Idle Time Scan and the Full System Scan to run during the same times.
Unless you're running your Scheduled Full System Scan when your system is NOT idle, the recommended setting is to set the Idle Time Scan to OFF when you have scheduled a Full System Scan.
First of all, allow me to thank you for your intervention. With the first part of your answer I'm OK.
But then you said:
"Unless you're running your Scheduled Full System Scan when your system is NOT idle, the recommended setting is to set the Idle Time Scan to OFF when you have scheduled a Full System Scan"
But my Scheduled Full System Scans are happening when the System is NOT Idle, indeed. Then, it goes that, I can have a "setting of Idle Scans" set, for example, to "Weekly"?
"Unless you're running your Scheduled Full System Scan when your system is NOT idle, the recommended setting is to set the Idle Time Scan to OFF when you have scheduled a Full System Scan"
But my Scheduled Full System Scans are happening when the System is NOT Idle, indeed. Then, it goes that, I can have a "setting of Idle Scans" set, for example, to "Weekly"?
You certainly can. For example, I just setup my Full System Scan to be run at 3:00 PM EST (2 minutes after I scheduled it). My Idle Time Scan was turned OFF automatically by NIS, but after setting up the the Scheduled Scan, I set the Idle Time Scan to WEEKLY. Again, this was just a test.
What happened? The Full System Scan ran at 3:00 PM EST. No problems. Now, if I were to setup my Scheduled Scan to run instead at 3:00 AM (when my system would be Idle), I would definitely set the Idle Time Scan to OFF.
In your initial posts, the error displayed is that the scheduler couldn't find the path. Could you elaborate on how your system is set up, where you installed NIS09, drive letters, multiboot setup, anything that might affect this issue? Thanks!
[edit: corrected typos.]
Message Edited by Tony_Weiss on 12-06-2008 04:06 PM
First of all, there are no special arrangements for NIS09. It's installed on dive C:\Programs Files. Now on top line specifics, I'm on Windows Vista 32, Home Premium, with BIOS from American Megatrends Inc. v2001, Starting Address Segment F000h, release date 8/6/2007 and ROM 1024, and BaseBoard: ASUSTeK/P5KPL-VM. If you need Chassi Info I can provide. Maybe if we compare the two reports:
In contrast to yesterday's failure to launch report, I can provide you with the success story of today:
Now the path error, isn't there today, since today I managed to run the Scheduled Scan successfully. To be honest Tony I cannot think what kind of Info to provide you with, that can explain/justify this failure to locate the route path to the disc.
But if you think of some info in particular, I would be more than happy to provide you.
Please accept my apologies for delaying my answer. Please fell free to bother me anytime if you think of anything.
I wasn’t happy with having to have a password to setup a scheduled scan. My wife and I are the only ones with access to the computer and to set up a user account with a password just for a scan when you don’t need a password to log on to the computer is stupid.
But, I bit the bullet and set up a second user account with a password thinking I would set up the scan, go into Task Scheduler and edit the scan to run whether the user is logged on or not, and be done with it.
The scan doesn’t run. Task Scheduler shows a message of “user name or password is not valid”. The scan runs when scheduled if the second user account is logged on but not if the original user account is logged on.
I know I can simply password protect my original user account but now it’s the principle of the thing. Maybe this is a Vista Task Scheduler problem rather than Norton’s, but seems like too much work to run a scan when I know the computer will be idle rather than when Norton wants it to run.
in the upper right corner of your page.