Analysis and questions about NAV 2005

[Jeff Barnett]

I am using Win XP SP2 on a desktop computer with Norton 2005 (NAV2005)
as my anti virus solution. The computer setup includes fast user
switching and simple file sharing. Most of my work is done within a
limited (power) user account. I have identified several issues with
NAV2005 and want to determine if these are caused by (1) NAV2005 itself,
(2) XP which provides a specialized API for anti virus programs, or (3)
something idiosyncratic to my computer. Any analysis, shared
experiences, or observations would be appreciated. The issues concern
(1) scheduling scans and (2) automatic updates.

Scheduled Scans
1. Scans can only be scheduled by an administrative user
2. The scheduling user must be logged on (though not necessarily active)
for the scheduled scans to run
3. The scheduled user must close the scan GUI after a scan is run and
before the next scheduled scan run or the next run is elided.
4. While the GUI is up (after a scheduled scan completes) the computer
will not automatically enter S1 sleep state

Conclusions on Scheduled Scans
1. If you are not aware of 2 and 3 above, many scheduled scans will
never be ran
2. Energy is wasted

Automatic Updates
1. Automatic updates are scheduled as system tasks so no user needs to
be logged on
2. If any user enables automatic update (a) all users benefit and (b)
the NAV2005 status GUI correctly reflects virus definition currency to
all users
3. The NAV2005 status GUI only reflects that automatic update is enabled
to the single enabling user

Conclusion Automatic Updates
1. The GUI protocol is confusing

-- Jeff Barnett

 

[kenny]

Advice for everyone... KEEP AWAY FROM ANYTHING NORTON!

 

[Jeff Barnett]

Are you saying that you are using some AV product where you don't need a
user logged on to run scans, that your computer returns to sleep after
scans, and properly sorts out user status on its GUI? If, so what
product are you using?

-- Jeff

 

[Kerry Brown]

I am using Win XP SP2 on a desktop computer with Norton 2005 (NAV2005)
as my anti virus solution. The computer setup includes fast user
switching and simple file sharing. Most of my work is done within a
limited (power) user account. I have identified several issues with
NAV2005 and want to determine if these are caused by (1) NAV2005
itself, (2) XP which provides a specialized API for anti virus
programs, or (3) something idiosyncratic to my computer. Any
analysis, shared experiences, or observations would be appreciated.
The issues concern (1) scheduling scans and (2) automatic updates.

Scheduled Scans
1. Scans can only be scheduled by an administrative user
2. The scheduling user must be logged on (though not necessarily
active) for the scheduled scans to run
3. The scheduled user must close the scan GUI after a scan is run and
before the next scheduled scan run or the next run is elided.
4. While the GUI is up (after a scheduled scan completes) the computer
will not automatically enter S1 sleep state

Conclusions on Scheduled Scans
1. If you are not aware of 2 and 3 above, many scheduled scans will
never be ran
2. Energy is wasted

Automatic Updates
1. Automatic updates are scheduled as system tasks so no user needs to
be logged on
2. If any user enables automatic update (a) all users benefit and (b)
the NAV2005 status GUI correctly reflects virus definition currency to
all users
3. The NAV2005 status GUI only reflects that automatic update is
enabled to the single enabling user

Conclusion Automatic Updates
1. The GUI protocol is confusing

-- Jeff Barnett

I have installed NAV 2005 for customers but not actually used it myself.
Does the scheduled scan use it's own scheduler or the Windows Scheduled
Tasks? The Windows Scheduler doesn't like to run from an account that
doesn't have a password. It could be something similar causing the scheduler
problems. In order to read all the files the task must be run as a user that
has those permissions. You could try a user that is a member of the Backup
Operators groups and make sure the account has a password. To actually try
and heal or delete a file then again the program needs permission and an
administrator account is needed. Possibly using the FAT32 file system may
get around some of the permission issues. The GUI/update issue I don't have
any ideas

Kerry

 

[Jeff Barnett]

Jeff Barnett wrote:



I have installed NAV 2005 for customers but not actually used it myself.
Does the scheduled scan use it's own scheduler or the Windows Scheduled
Tasks? The Windows Scheduler doesn't like to run from an account that
doesn't have a password. It could be something similar causing the scheduler
problems. In order to read all the files the task must be run as a user that
has those permissions. You could try a user that is a member of the Backup
Operators groups and make sure the account has a password. To actually try
and heal or delete a file then again the program needs permission and an
administrator account is needed. Possibly using the FAT32 file system may
get around some of the permission issues. The GUI/update issue I don't have
any ideas

Kerry

The window's scheduler is used and, yes, a password is needed. It must
be done by an administrative user. I believe the core problem is the
GUI: NAV wants to pop the GUI when it starts the scan and needs the user
to click the close button after the scan is complete. It can't pop the
GUI unless the user is logged on. I think the scan itself runs with
system-level privileges. I'm using NTFS so your conjecture about about
FAT 32 may be a factor but I can't verify.

-- Jeff

 

[kenny]

free version of www.avast.com

Better than NAV 1000 times