We've installed MSAS on our college's computers, with scheduled scans once a
day, not displaying scan results or progress (lest the users "opt out" while
the scan is running), and "Automatically remov[ing] items." However, in all
the testing we've done (imagine my feeling of awkwardness when tasked with
infecting a test computer!), the scans will DETECT ad/spy/mal-ware, but not
remove or quarantine. Users actually have admin rights on the machines, but
they are not the installing/configuring accounts. Is this the problem?

Any thoughts?
--
-b

Blissfully ignorant of all things "important" since 1964...

Microsoft AntiSpyware beta 1 does not scan multiple user accounts. This
means, you have manually log into each account "Administrator" and run the
scan. Also try running scans in safe mode.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

"Baaab" <(E-Mail Removed)> wrote in message
news:19B66050-5516-4076-84C2-(E-Mail Removed)...
> We've installed MSAS on our college's computers, with scheduled scans once
> a
> day, not displaying scan results or progress (lest the users "opt out"
> while
> the scan is running), and "Automatically remov[ing] items." However, in
> all
> the testing we've done (imagine my feeling of awkwardness when tasked with
> infecting a test computer!), the scans will DETECT ad/spy/mal-ware, but
> not
> remove or quarantine. Users actually have admin rights on the machines,
> but
> they are not the installing/configuring accounts. Is this the problem?
>
> Any thoughts?
> --
> -b
>
> Blissfully ignorant of all things "important" since 1964...

You hit the nail on the head with the question about the user account not
being the one that installed the app.

The current release only supports the administrator account that installed
the app.

Multiple user account support should be included in Beta 2, likely to be
released later this year.

Alan

"Baaab" wrote:

> We've installed MSAS on our college's computers, with scheduled scans once a
> day, not displaying scan results or progress (lest the users "opt out" while
> the scan is running), and "Automatically remov[ing] items." However, in all
> the testing we've done (imagine my feeling of awkwardness when tasked with
> infecting a test computer!), the scans will DETECT ad/spy/mal-ware, but not
> remove or quarantine. Users actually have admin rights on the machines, but
> they are not the installing/configuring accounts. Is this the problem?
>
> Any thoughts?
> --
> -b
>
> Blissfully ignorant of all things "important" since 1964...

One important thing to note is any user that can log onto the system CAN
configure MSAS since it isn't password protected.

You will have to wait until the enterprise version (will have to purchase)
for password protection and configuration by another system (i.e., the IT
administrator's system).

Alan

"Alan" wrote:

> You hit the nail on the head with the question about the user account not
> being the one that installed the app.
>
> The current release only supports the administrator account that installed
> the app.
>
> Multiple user account support should be included in Beta 2, likely to be
> released later this year.
>
> Alan
>
> "Baaab" wrote:
>
> > We've installed MSAS on our college's computers, with scheduled scans once a
> > day, not displaying scan results or progress (lest the users "opt out" while
> > the scan is running), and "Automatically remov[ing] items." However, in all
> > the testing we've done (imagine my feeling of awkwardness when tasked with
> > infecting a test computer!), the scans will DETECT ad/spy/mal-ware, but not
> > remove or quarantine. Users actually have admin rights on the machines, but
> > they are not the installing/configuring accounts. Is this the problem?
> >
> > Any thoughts?
> > --
> > -b
> >
> > Blissfully ignorant of all things "important" since 1964...