Re: Updated AV database via run-as-admin, need reboot?
Mister....@gmail.com
> <Mister....@gmail.com> wrote:
> > I'm running Symantec AntiVirus, Full version 10.0.2.2000 on Windows XP.
> > I usually log in as a non-admin account. However, the option to
> > update the virus definitions is only accessible as administrator.
> > Therefore, I use run-as to invoke the AV application (without doing
> > anything special to terminate the AV running on the non-admin's system
> > tray). I assume that this updates the database definition files, but
> > do I have to terminate and relaunch the AV running on the nonadmin's
> > system tray before those files are read? The only way I know of doing
> > this is to reboot (or maybe log out and log back in). This is was I
> > was trying to avoid, since I have many documents open to different
> > locations. I also haven't set up auto-update, since this is usually a
> > standalone computer. Thanks.
>
> I've found stopping & restarting the "Symantec antivirus" service
> updates the virus definitions. Perhaps stop & restart the service via a
> batch file automatically every day?
Jeff, thanks for your suggestion. I just tried it, but it didn't seem
to work. I logged into the nonadmin account and Symantec AV was
already on system tray (as expected). I used Run-As to access the
Services console as admin. I stopped and started the AV. The AV icon
was on the system tray again. I then used Run-As to launch the AV as
admin and perform an update, which it promptly did. This means that
starting and stopping the AV service did not update the AV with new
definitions.
I did not set up automatically scheduled downloads because it is a
standalone computer most of the times. I'm not sure I want to check
for updates every time I connect (especially over low bandwidth
connections).
I can use Run-As to launch the AV as admin for purposes of updating the
virus definition files, but I'm still not sure whether the AV image
that is running under the nonadmin account will be using those
definitions. If I had to guess, I'd say yes; this is because the AV
definitions are presumably huge, which may preclude the possibility of
the AV image working with its own "working copy" (whether in memory or
on disk). I think it unwise, however, to treat such a guess as fact.
As well, it is possible that there is just one image of the AV, and the
LiveUpdate option may be enabled depending on the prevailing user (the
user that is logged on, or the currently active logged-on user in the
case of fast user switching). Again, it's just a guessed-at
possibility, which I wouldn't rely on at this point.
Why on earth would the default be to lock out nonadmin initiation of
LiveUpdate? Rhetorical question, really (since it doesn't matter at
the moment). Currently, my aim is to not only update the AV definition
files, but so to be sure that those definitions take effect i.e. have
them used by the AV image running under the nonadmin account. All this
without forcing the nonadmin account to log out.
Fred
P.S. Follow-ups set to
symantec.support.winnt.nortonantivirus.liveupdate, alt.comp.virus, and
alt.comp.anti-virus. What distinguishes the last 2 groups anyway?
edgewalker
<Mister....@gmail.com> wrote in message news:1155397897.9...@m79g2000cwm.googlegroups.com...
> P.S. Follow-ups set to
> symantec.support.winnt.nortonantivirus.liveupdate, alt.comp.virus, and
> alt.comp.anti-virus. What distinguishes the last 2 groups anyway?
Mostly the same people in both groups. Generally aca-v has better S/N
ratio.