Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NAV'03: scan auto-scheduling issues

Status
Not open for further replies.

peva2

IS-IT--Management
Apr 4, 2003
10
US
(I searched 6 months archives on "scan schedule automatic" - all words - with no results - I would have thought that such problems as these would have been discussed to death if they were common - sorry if I missed something.)

Background: Company with 20 networked computers; OS's are all Windows - 98, 2000, & XP.
Problem: Several consistent problems with automatic scheduling of scans, to wit
--1. With the default 8pm Friday automatically scheduled scan time, I assumed originally that if the computer happened to be off at the set time, that, at the minimum, NAV would prompt the user at the next bootup that "The scan was missed, do you want to scan now" or something similar. Didn't NAV use to do that years ago? Anyway - is this a bug, or is there a way to fix this?
--2. After experiencing item 1. for a few weeks, I went around to all the computers and set the scan schedule to some morning weekday when the computers will likely be on. Upon checking several weeks later, find that scans are not happening. I checked the scheduled time, and it has changed to a P.M. time or a week end day (when computers are off). Individual users insist that they are not changing the schedule time or stopping a scan (happens on the computer I use too).
--3. Sometimes, simlar to 1. above, but schedule time is staying as I set it, but for some reason the scan is not happening (again, no one 'fesses up to changing the scan schedule, and I would have trouble believing that that is the case in all cases).

TIA for any help. Right now our only work-around is to beat on our people to regularly do manual scans (not a good solution).

PEVA2
 
Oops - Item 3. in my original message should have started out "Sometimes, similar to 2. above,...".
 
I came back to post the solution to my own problem so everyone can learn.

What happened is that we changed our network server a couple of months ago, and everybody's ID and password got changed. Well - Windows Scheduler needs that info. to be correct to run the task. The WIN 98 scheduler is less sophisticated (no ID and password) and so didn't have a problem - simpler can be better many times. Now all the weird details of the problem make perfect sense.

The solution (support doc came in a Symantec support e-mail response. Funny thing is that when I used their own site's search engine on their support documents a couple of days ago using a couple of words that are *in* the title of the document that their e-mail pointed to, that document didn't come up - must be job security for their support people.

Anyway - enter the correct ID and password on each computer in Windows Scheduler, and problem is fixed.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top