Observations of the Beta Release

Re: Cookies - What would be extremely nice is to see an
anti Spyware program that can deal with issues like
cookies which have been distributed to roaming profiles
and cached on the local machine. This beta release
doesn't even touch roaming profile cookies on the server
(but then, it doesn't pick them up in the local profile
either.) These are subsequently picked up by programs
like Ad-Aware.

Re: Registry Entries - I had variable results with this.
On one computer - it would remove the entries when
prompted to. On the other, it would only "Ignore"
(presuming that it was really ignoring) even if prompted
to "Remove". It did serve as a good reference for
manually removing the registry entries but I would assume
this is something that the software should be able to
handle.

Re: Logging - I was disturbed by the way that the logging
is set up. It appears that information is only available
pertaining to the last scan. So, assuming that you're
auto scanning daily... and it finds something on Friday
or Saturday - but not on Sunday - then Monday shows "0"
results and any record of Friday's or Saturday's results
don't seem to be available. Any cumulative or
significant historical results seem to be lost - which
for an IT guy, makes this awfully hard to track down
issues.

Re: Topology: As with other spyware programs - I've yet
to find one that I can run on workstations through an
interface on a server (or a web interface on a server)
and get results from across the network through that
interface. This is what's really needed out here!

Excellent post! I found the same to be true in my case,
but hadn't noticed the logging issues yet.


>-----Original Message-----
>Re: Cookies - What would be extremely nice is to see an
>anti Spyware program that can deal with issues like
>cookies which have been distributed to roaming profiles
>and cached on the local machine. This beta release
>doesn't even touch roaming profile cookies on the server
>(but then, it doesn't pick them up in the local profile
>either.) These are subsequently picked up by programs
>like Ad-Aware.
>
>Re: Registry Entries - I had variable results with this.
>On one computer - it would remove the entries when
>prompted to. On the other, it would only "Ignore"
>(presuming that it was really ignoring) even if prompted
>to "Remove". It did serve as a good reference for
>manually removing the registry entries but I would assume
>this is something that the software should be able to
>handle.
>
>Re: Logging - I was disturbed by the way that the logging
>is set up. It appears that information is only available
>pertaining to the last scan. So, assuming that you're
>auto scanning daily... and it finds something on Friday
>or Saturday - but not on Sunday - then Monday shows "0"
>results and any record of Friday's or Saturday's results
>don't seem to be available. Any cumulative or
>significant historical results seem to be lost - which
>for an IT guy, makes this awfully hard to track down
>issues.
>
>Re: Topology: As with other spyware programs - I've yet
>to find one that I can run on workstations through an
>interface on a server (or a web interface on a server)
>and get results from across the network through that
>interface. This is what's really needed out here!
>.
>

>
>Re: Logging - I was disturbed by the way that the
logging
>is set up. It appears that information is only
available
>pertaining to the last scan. So, assuming that you're
>auto scanning daily... and it finds something on Friday
>or Saturday - but not on Sunday - then Monday shows "0"
>results and any record of Friday's or Saturday's results
>don't seem to be available. Any cumulative or
>significant historical results seem to be lost - which
>for an IT guy, makes this awfully hard to track down
>issues.
>

Maybe you could try clicking on 'Tools' / Spyware Scan /
View Spyware Scan History.
I also saw a message about being able to view 'archived'
logs somewhere...