If you want to eliminate all real-time protection, the gui can be
misleading--the best way to do this is to follow the "workaround" paragraph
in this KB article:
http://support.microsoft.com/kb/892375 End users may be prompted to allow or
block administrative actions that originate from a central management tool
after they install Windows AntiSpyware (Beta) on a computer that is managed
by Systems Management Server 2003
(This article may also be of interest to your client, depending on the size
of their network--it discourages installation in a managed environment--with
good reason.)
It'd be interesting to see whether eliminating the real-time protection,
which is provided by a driver that uses a shellexecute hook--eliminates your
performance issue. I suspect that this would indicate a software issue in
your environment.
Many details about this beta product will change significantly with the
release of beta2, which should come later this year or early next--one way
for the client to deal with this issue would be to back off and look again
when beta2 is released.
--
"Paul Sjoerdsma" <paul.nospam.@pasoftware.nl> wrote in message
news:(E-Mail Removed)...
> Removing and re-installing didn't make a difference. The errors.log
> was only around 500Kb.
> The funny thing is, even if I turn off all the security agents, the
> application is still slow.
>
> Hopefully the new beta will behave better. Now convinve our clients
> that running MS Antispyware Beta is not always a good thing and that
> the Beta part in the name is there for a reason.
>
> regards
> Paul
>
>
> On Tue, 8 Nov 2005 13:38:14 -0500, "Bill Sanderson"
> <(E-Mail Removed)> wrote:
>
>>Throughout the beta we've seen that certain installs of Microsoft
>>Antispyware involve high CPU loads and significant impact on both
>>individual
>>apps and the general use of the machine.
>>
>>I'd recommend trying this set of steps to see whether it provides relief
>>on
>>a given machine.
>>
>>Beta2 will be quite different, I believe, but it won't be available before
>>year end, if then.
>>
>>1) uninstall Microsoft Antispyware
>>2) delete \program files\microsoft antispyware and all subfolders
>>
>>You will lose access to all quarantined items, history, and custom
>>settings
>>
>>3) reinstall Microsoft Antispyware.
>>
>>This may fix a variety of ills. One easy thing you could check is whether
>>the errors.log file in the \program files\microsoft antispyware folder is
>>large. If so, delete it. Growth under earlier builds was uncapped and
>>could be rapid--2 gig files under NTFS were possible. Growth of this file
>>is now capped, so simply deleting it will fix that issue.