Microsoft Antispyware ADM Template

  • Thread starter Thread starter Chris Murray
  • Start date Start date
C

Chris Murray

I am also looking into using AntiSpyware across my network
but no ADM files are to be found. I have found a web site
explaining how to script MAS but it has been since removed
from the scripting pages. If anyone has a link to MS's
update script page for MAS or has some sample working code
let me know. I can adapt any language but VBS is
preferred.

http://www.microsoft.com/technet/scriptcenter/resources/art
icles/antispy.asp
 
I'm somewhat startled at the number of folks wanting to deploy an
unsupported beta application which clearly states that it should not be
installed on production machines, across their enterprise.

I just checked the link to the unattended install in the information below,
and it seems still good:
---------------------------------------
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

Scripting issues:

http://www.microsoft.com/technet/scriptcenter/resources/articles/antispy.mspx

Unattended uninstall:

MsiExec.exe /X {536F7C74-844B-4683-B0C5-EA39E19A6FE3} /L *vx /Log
c:\msas.log /quiet

Unattended Install:

http://www.overdose.net/docs/msas_silent_remote_install.txt
 
Bill - I can easily understand why so many people want to
deploy this software, even though it's "beta".

The reason is that the problem it relieves today is so
pressing that people are willing to live with the risks.

This is reinforced by a few important facts:

- people have found MSAS beta to be much more effective
than ANY other free scan tool which is allowed for
corporate use (eg, not 'free for personal use only')

- people have found MSAS to cause problems which are far
smaller in impact and frequency than spyware itself causes.

If MSAS wasn't as good as it is, and the spyware problem
was not as severe as it is, then you would not see the
knocking down the doors to deploy this beta software into
production environments.

I'm sure there are "IT cowboys" out there who would just
deploy without thinking about it, but there are plenty
of "IT realists" who are looking at MSAS, running internal
pilots, collecting data, and making coldly calculated risk-
benefit decisions that come down conluding: it's safer to
use MSAS beta than not to use it, and we've got the
numbers to prove it.

-Dan Becker
 
I don't doubt the accuracy of you reasoning. I installed this beta on all
the machines I admin on the first day of availability, and haven't regretted
that for a minute. (cowboy probably isn't an unreasonable designation......)

The reason I post that wording is that I want to make sure that folks in
this situation are really taking notice of the situation. If I really felt
that it was a completely unreasonable and dangerous decision to take, I
wouldn't then go ahead and post the other links that constitute the
available information I have about how to do the job.

So--I'm just trying to be sure that people are thinking about this
rationally.
 
Back
Top