While checking my logs in ADNM, I noticed that several clients have Canceled under the status column. Most say Done, and a couple say Processing. I have the scan-job set to do a boot-time-scan around 2330 every night. How can it be canceled or is this a sign of some other error? Furthermore, a couple say Processing. Why would that be there since 2330 the night before? I also rebooted one of the PCs and it went into the scan? I have the firewall turned off and I can get to the chest from the ADNM PC - which tells me nothing is blocking communications between the 2 PCs. Any idea what’s going on here?
Canceled could mean that a user canceled the scan when he turned on the computer in the morning.
Processing could mean that the computer was not restarted since the scheduled time, or the task expired before the restart.
The boot-time scan is not started immediately at the scheduled time but rather after following restart. Restarting can be configured at the Reboot page.
Two things I see wrong with that… 1-It gives a message, during the boot-time scan, that states one cannot cancel the action. 2-I believe the PCs are to be rebooted shortly after the job is sent out. When I 1st set this up, I sent out the job manualy and nothing happened…or so I thought. By the time I made a couple scripts in the Windows Sceduled Tasks folder that would reboot the PCs at night, I had PCs rebooting all over the place. Haha - needless to say, I pissed off a couple people that day! So, I know they are to be rebooted soon after the scan job goes out. I just don’t know why some are taking almost 12 hours. Even if they were timing out, you’d think I’d get some sort of error saying that… I dunno - I’m up for just about any suggestion. Maybe I’m wrong…it’s happened a couple times before
So the session is CANCELED even though you configured the task not to be abortable ?
And the session stays as PROCESSING even though the computer was restarted after the schedule time ?
If you restart the computer by your own means you should also consider the delay between the schedule time and the moment when the task is popped by a client (it is 10±5 minutes by default). This is also true for manual start of the task.
And the scan really runs 12 hours or the session just shows as PROCESSING all this time ?
Yes, I have it “set” so that it can’t be aborted. It says it can’t in the blue/white screen just seconds before the scan. Yet, somehow, it shows up as CANCELED in the “logs.”
I guessing these other PCs aren’t getting rebooted and that’s why they remain PROCESSING. If I go and manually reboot them, they go into the scan without issue. However, if I don’t reboot them, the status will show up as PROCESSING all the time. On these same PCs, I can manually send the job down and it won’t reboot - I have to reboot it.
Yes, I have it "set" so that it can't be aborted. It says it can't in the blue/white screen just seconds before the scan. Yet, somehow, it shows up as [i]CANCELED[/i] in the "logs."
Didn’t you select ‘stop task’ in the virus actions of the task, it could be the reason.
I guessing these other PCs aren't getting rebooted and that's why they remain [i]PROCESSING[/i]. If I go and manually reboot them, they go into the scan without issue. However, if I don't reboot them, the status will show up as [i]PROCESSING[/i] all the time. On these same PCs, I can manually send the job down and it won't reboot - I have to reboot it.
And what option did you select on Reboot page of the task ?
In the task properties, under execution, I have it set for boot-time scan. I do not have the check boxes set to allow for an abortion (yeah, that sounds bad, I know!) or skip actions in the system files. I also have it set to reboot in 30 seconds.
I think I may have found a problem though. Under task properties, under processing, you can set the number of concurrent push jobs. The default is 50 and I have more than 50 in here. I have set that to 200. I don’t have 200 clients but I might as well keep it high so I don’t hit the limit any time soon.
New problem while attempting to figure out the other problem:
Yesterday, I set up another ADNM in the same company. I’m hoping to take some of the stress off the other machine and devide the jobs up. They have 2 buildings and a point-to-point between them so they are all on the same network. I tested it on a few machines that are set up as kiosks so I’m not too worried about infections - they’re normally clean. I made the install package and uninstalled the old managed client (that pointed to the old ADNM PC an hour away) & installed the new package (that is pointed to the knewly created ADNM PC). They all rebooted and the ADNM saw them. After a while, they all showed up and OFFLINE. Well, all but 1! 1 out of 6 ain’t bad, right!? :-[ The Windows XP Home PCs have the firewall turned off and there shouldn’t be any problems. After all, all I did was uninstall the old client software & install the new. The old ADNM doesn’t see these PCs either. With my head scrambled, I left for the day. Ahhh, I love my job…SNAFU!
The logs (especially \data\log\error.log) should tell us more. BTW it would be more sensible to move to a different thread, as this has nothing to do with the original problem (scheduled boot-time scanning).
So, I know they are to be rebooted soon after the scan job goes out. I just don’t know why some are taking almost 12 hours. Even if they were 