Must admin be logged on for scheduled NAV to run?

[nomail1983]

I have scheduled Norton Antivirus to run automagically every Monday at
11pm.

Must an administrator account be logged on in order for NAV to run?

Or does it run even if no administrator account is logged on?

 

[nomail1983]

Clarification....

I have scheduled Norton Antivirus to run automagically every Monday at
11pm.
Must an administrator account be logged on in order for NAV to run?
Or does it run even if no administrator account is logged on?

Obviously, the computer must be turned on and at least booted to the
welcome screen.

 

[Jeff Barnett]

I have scheduled Norton Antivirus to run automagically every Monday at
11pm.

Must an administrator account be logged on in order for NAV to run?

Or does it run even if no administrator account is logged on?

I had a great deal of difficulty getting NAV 2005 to run scheduled
scans; note that other NAV 200x may be different. First, Norton puts the
scan under the administrator account and sets it up funny. I changed
settings to (1) run when logged in and (2) break suspend to run. I keep
the administrator logged on but not necessarily active. It turns out
that this is necessary because the scan pops a GUI and needs an account
to "pop" it in. Further, the scan is not considered complete until you
click the finish button on that GUI. That means you need to visit the
account (switch users to it) after the scan runs but before the next one
is scheduled. I have also noted that the computer will not drop back
into standby until that GUI is dismissed. It's too bad Norton didn't
code the scheduled scan to run as a system process and send a message if
and only if a problem was found.

-- Jeff Barnett

 

[Guest]

No it doesn't need to be the admin that is logged on, as long as you have
given norton the proper account password, it will log on and run, as long as
the password and account is valid.

 

[Guest]

Interesting, I keep my account logged in (i'm admin level) and did notice
that scan is finished popup, though I've never had a problem with the scan
running.
it doesn't run under admin, but under my account name.

 

[nomail1983]

I keep
the administrator logged on but not necessarily active. It turns out
that this is necessary because the scan pops a GUI and needs an account
to "pop" it in. Further, the scan is not considered complete until you
click the finish button on that GUI. That means you need to visit the
account (switch users to it) after the scan runs

Thanks. Those are the reasons why I suspected someone must be logged
in, but I wasn't sure. Kinda like proving that the refrigerator light
turns off when the door is closed . I am not in a position where I
can test it before I needed the answer.

 

[nomail1983]

Interesting, I keep my account logged in (i'm admin level)
[....]
it doesn't run under admin, but under my account name.

That is what I mean by "administrator account". That is not the same
as logging on as the user Administrator.

Coincidentally and quite by accident, the scheduled NAV scan ran while
I was logged on in both an administrator account and a limited account,
and the limited account was active. NAV ran in the administrator
account, which I discovered when I switched to that user.

So I believe Jeff is right: at least one administrator account must be
logged in, albeit not necessarily active. That makes sense to me
because if NAV finds problems, (hopefully) only an administrator user
take the appropriate actions.