HOWTO scan all local disk with Remote Admin?

Hi there,

using the Remote Administrator I wanted to define a task to scan all local disks. In the "On-Demand Scan" window I deselected C: and selected "All local drives".

But the logfile of the scan looks like this:

=====================
Log Details
Scanning Log
NOD32 version 1.881 (20040930) NT
Operating memory - is OK
number of scanned files: 2
number of viruses found: 0
time of completion: 16:40:22 total scanning time: 1096641622 sec (304622:40:22)
=====================

It didn't scan anything at all.

The logfile of an On-Demand Scan in which's definition I explicitly selected the C: and the D: drive looks like this:

=====================
Log Details
Scanning Log
NOD32 version 1.881 (20040930) NT
Operating memory - is OK
date: 1.10.2004 time: 16:42:20
Scanned disks, directories and files: C:; D:
C:; D:
C:\hiberfil.sys - error opening (file locked)
C:\pagefile.sys - error opening (file locked)
number of scanned files: 13238
number of viruses found: 1
time of completion: 16:45:46 total scanning time: 206 sec (00:03:26)
Notes:
[4] File cannot be open. It is being exclusively used by another application or operating system.
=====================

Any idea, what I am doing wrong or how I am suposed to define an On-Demand Scan for a large number of clients with varying numbers of local disks?

Thanks a lot!

Cheers.
+rainer

 

I have the same problem. It is same problem with configuration files.
Right now, when I'm using "On-Demand Scan", I set it to check C&D drive and select "All Local drives"

 

The way I did it was I created a config file for just scanning and cleaning.
1. Click on "Create a New Task" on the tool bar.
2. Choose "On Demand Scan" and click OK.
3. It should give you the option to View of Edit. Click Edit.
4. After you have made your changes what you want save it, and name it what ever you want.
5. Click Back to Console.
6. Make sure all local Drives is checked and clean automaticaly.
7. Click next. From the drop down menu choose pc, and click next.
8. Click finish.

Hope this helps.

 

Hm, I don't see the fundamental difference to my method. What drives did you select in the configuration editor?

 

I selected the option for all local drives. If you don't create a config file that you want it uses some temporary one.

 

Ok, I changed the config file, but nonetheless it only scans the drives I selected in the config file and not all local drives....

 

The scanning of all local drives can be easily acomplished by scheduling a task that will trigger nod32.exe with the /local parameter (also you can specify additional parameters per your needs).

 

Hi hubo:

Just as Marcos stated, a Scheduled Task using Execution of an external application may be a better alternative depending on your reasons. Here is an example:

c:\program files\eset\nod32.exe

/local /clean /delete /mapi- /arch+ /pack+ /ah /program /scroll+ /log+ /quit+

Use a /break- if you do not want the ability to close/terminate the cleaning process.

Caution on this should be taken if you do not know the environment is safe from False Positives as the quarantine feature is not available through command line scanning (it has been requested).

I hope this helps.

 

I will try to do a test on my own.

 

Thank you for your help Marcos and rumpstah!

I tried it out and it worked well with the exception that the scan task scheduled as an On-Demand-Scan runs in the background with no windows etc. opening but the scan task scheduled as an external application opens the NOD32 Antivirus Scanner window.

I would prefer if the job runs in the background. Is there a way to accomplish this?

 

Hi hubo:

I asked for the same feature. Unfortunately it has not been implemented as far as I know. This is the reason for the Execution of an external application. I like the window popping up so people can see how well/fast NOD32 works.

 

Do you want to add this one to the list in "Future Changes to Nod32"?

Cheers

 

I think it would be a good idea to add silent Scheduled tasks for cleaning.

 

Done.

Cheers

 

Just because im curious: is the fact that the scheduling of On-Demand-Scan's of local disks via the RA doesn't work considered to be a bug? Will this be fixed?

 

Hi Hubo,

As far as I can tell I have no problems scanning Local drives. In the NOD32 Configuration Editor -> Under NOD32 scanner -> settings -> "Local Drives" set to yes.

hope this helps.

Brian

 

Hi Bsilva,

I don't want to repeat my initial posting. Could you please read it and tell me if I did something wrong. Maybe I overlooked something.

Thank you.

+rainer

 

When you select new task -> On Demand Scan -> Then click edit. Than look under the settings to see if you have all local drives set to yes. I see that you have selected all local drives on the New task wizard, but I want to make sure that it's set in the config file. That's what the scan is going to use.

 

Ok, I see. Did what you told me. In the config Editor "Selected Drives" is empty and "Local Drives" is "Yes".

 

In the selected drives I have C:

 

If I select C: then I have C: in the Config-Editor. But it also scans only C: and not all local drives...

 

I'm not sure if this has anything to do with it. But under Profile in the NOD32 Scanner I have set to My Profile

Here is one of my logs that I scheduled with RA.

Log Details
Scanning Log
NOD32 version 1.885 (20041006) NT
Command line: /config=My Profile
Operating memory - is OK

date: 5.10.2004 time: 23:00:27
Scanned disks, directories and files: C:; D:; E:; F:
C:; D:; E:; F:
C:\pagefile.sys - error opening (file locked)
C:\Documents and Settings\LocalService\NTUSER.DAT - error opening (file locked)
C:\Documents and Settings\LocalService\ntuser.dat.LOG - error opening (file locked)
C:\Documents and Settings\LocalService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - error opening (file locked)
C:\Documents and Settings\LocalService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG - error opening (file locked)
C:\Documents and Settings\NetworkService\NTUSER.DAT - error opening (file locked)
C:\Documents and Settings\NetworkService\ntuser.dat.LOG - error opening (file locked)
C:\Documents and Settings\NetworkService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - error opening (file locked)
C:\Documents and Settings\NetworkService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG - error opening (file locked)
C:\WINDOWS\system32\config\default - error opening (file locked)
C:\WINDOWS\system32\config\default.LOG - error opening (file locked)
C:\WINDOWS\system32\config\SAM - error opening (file locked)
C:\WINDOWS\system32\config\SAM.LOG - error opening (file locked)
C:\WINDOWS\system32\config\SECURITY - error opening (file locked)
C:\WINDOWS\system32\config\SECURITY.LOG - error opening (file locked)
C:\WINDOWS\system32\config\software - error opening (file locked)
C:\WINDOWS\system32\config\software.LOG - error opening (file locked)
C:\WINDOWS\system32\config\system - error opening (file locked)
C:\WINDOWS\system32\config\system.LOG - error opening (file locked)
Directory path D:\ is invalid.
F:\pagefile.sys - error opening (access denied)
number of scanned files: 95904
number of viruses found: 0
time of completion: 23:07:17 total scanning time: 410 sec (00:06:50)

Notes:
[4] File cannot be open. It is being exclusively used by another application or operating system.

 

Sorry You were right. It was my config file that I had it set to hardcoded. I tried not to use a config file and didn't scan all local drives.

 

Mine looks like this:

Log Details
Scanning Log
NOD32 version 1.885 (20041006) NT
Operating memory - is OK

date: 6.10.2004 time: 16:47:48
Scanned disks, directories and files: C:
C:
C:\hiberfil.sys - error opening (file locked)
C:\pagefile.sys - error opening (file locked)
C:\System Volume Information\_restore{4060549C-13E1-495C-8E62-67955F590BB3}\RP72\A0009828.com - Eicar test file
number of scanned files: 12819
number of viruses found: 1
time of completion: 16:51:29 total scanning time: 221 sec (00:03:41)

Notes:
[4] File cannot be open. It is being exclusively used by another application or operating system.

 

I did another test and I got it to scan certain drives. The ones I selected. I would consider this a bug.