Re: Scheduled Server scan does not log events - Trend Micro WFBS 5.1

Tech-Archive recommends: Fix windows errors by optimizing your registry

Paul,

Yes as you say Trend Micro is definately letting itself down with the
reporting and logging facilities. Personally I preferred it before they
joined the quest to make everything HTML driven and had a proper Win32 based
console, why does every manufacturer feel the need to make everything Web
enabled!

I had not noticed that the last scan time is listed on that screen, thanks
for reminding me. Problem is it only shows the dateTime of the last full
scan, no record of start time or duration.

Actually the Scheduled Exchange Server Scans are recorded in Log
Query-Exchange Server-Scan event logs. It is only the Scheduled
Desktop/Server Scans which are not recorded in Log Query-Desktop/Server-Scan
Event logs, probably because there is no 'Scan Event logs' option there
looks like it has been forgotten.

Nick


"Paul Shapiro" <paul@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:O$nXZrzmJHA.1252@xxxxxxxxxxxxxxxxxxxxxxx
This is one glaring weakness with Trend. I've never been able to find good
reporting. As far as I can tell, if a computer is off at the scheduled
scan time, it will not perform the scan. I know it can't scan when it's
off, but I would like an option to enable the scan the next time the
computer is turned on.

All I've found for reporting is the summary on the Security Settings tab.
Click on the Desktops group and the right pane shows a very small summary
of each computer's status. Included is the last date a scheduled scan was
run. But if a computer was shut down during a scan, the only indication is
the scan start time is listed as the scan time, while if the scan
completed it shows the scan end time. There's a summary of issues, but you
have to go to Reports-> Log Query and hunt through the various kinds of
logs to try and find details. Since the issue summary can include older
data than the log files, which default to purging after 2 weeks, you might
not find the details anyway.

You can see the scheduled scan settings under Scans->Scheduled Scans. You
can set the cpu utilization to high, medium or low. The medium and low
settings add some delay time between each file scan to affect cpu
utilization. On my workstation, where I notice the scan running, on High
it takes about an hour and impedes work with a dual-core cpu. On Low it's
still noticeable but I can continue working pretty smoothly, and it takes
about 5 hours to scan.

"Nick" <NoOne@xxxxxxxxxxx> wrote in message
news:OL8easymJHA.500@xxxxxxxxxxxxxxxxxxxxxxx
Can anyone explain where in WBFS 5.1 console I can find a log of when the
Scheduled Server Scan is running? I would expect to find them in:
Reports - Log query - Type: Desktop/Server but no record of it
there.

We have recently discovered that our Sunday morning Scheduled Server Scan
is taking four and a half hours to complete and triggering high CPU
alerts in the process. A diagnostic list of what drives it is scanning
and at what times would allow us to see which drive is causing the
problem.



.

Relevant Pages