Large Managed Environment Question

  • Thread starter Thread starter Marco Nielsen
  • Start date Start date
M

Marco Nielsen

Since there is no official support on this product, yet
people are installing it to combat the war on Spyware. I
have some questions:

Before we have issues with our domain Login Scripts and
SMS deployments, how do we automate the steps listed in
this article?

http://support.microsoft.com/?id=892375

I don't see how we can execute workaround step 1 in an
automated fashion and prohibet this problem in our
environment.

If we can't do this, we will be forced to prohibet the
installation of the AntiSpywareBeta.exe through a GPO to
keep it off our production clients worldwide.

Any thoughts?

|\\arco..
 
Hi Marco,
This MWAS product isn't meant for Enterprise deployment. If I were you, I
too would block it at this time.
I have tested this on domains, and have blocked scripts, so yes, you could
have a problem.

There will be an Enterprise version MS Anti Spyware product coming out, tho
we haven't heard any timelines yet.

Ron Chamberlin
MS-MVP
 
I would recommend that you block it.

If you want all the options, here's my list of "useful" information for
managed environments:
(most useful may well be blocking it, perhaps allowing it to run, but
disabling real-time protection (see the workaround section of the first KB
reference)--and the unattended uninstall--for those situations where it is
already in place.

[Managed environments, scripting, turning off real-time protection]

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
 
Thanks Ron for the quick reply. Yes, I think the only
thing we can do is block it totally..

|\\arco..
 
Thanks Bill, I agree with you the only thing that it
appears to be done is block it and force the uninstall
one the managed clients that already have it..

As you referenced the same article I did,
http://support.microsoft.com/?id=892375, it still appears
no one has a good idea on how to automate step 1 of the
article to make it useful to be used in any managed
environment..

Thanks for the great FAQ!

|\\arco..
-----Original Message-----
I would recommend that you block it.

If you want all the options, here's my list of "useful" information for
managed environments:
(most useful may well be blocking it, perhaps allowing it to run, but
disabling real-time protection (see the workaround section of the first KB
reference)--and the unattended uninstall--for those situations where it is
already in place.

[Managed environments, scripting, turning off real-time protection]

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/a rticles/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.t xt

--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

Since there is no official support on this product, yet
people are installing it to combat the war on Spyware. I
have some questions:

Before we have issues with our domain Login Scripts and
SMS deployments, how do we automate the steps listed in
this article?

http://support.microsoft.com/?id=892375

I don't see how we can execute workaround step 1 in an
automated fashion and prohibet this problem in our
environment.

If we can't do this, we will be forced to prohibet the
installation of the AntiSpywareBeta.exe through a GPO to
keep it off our production clients worldwide.

Any thoughts?

|\\arco..
Click to expand...
Click to expand...
 
The FAQ is Mark L Ferguson's work--I've contributed odds and ends to it, but
he was responsible for initiating it and maintaining it.

Yes--step one of that article appears to require visiting each machine. I
have seen some discussion around the idea of making the change to the
settings in that article, observing which of the .GCD files changes, and
placing that file, with those changes in effect, on each machine via some
mechanism. This may well be possible. Whether worth the effort or not, I
can't say--not sure about issues of number of machines, length of the beta,
etc....
--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

Marco said:
Thanks Bill, I agree with you the only thing that it
appears to be done is block it and force the uninstall
one the managed clients that already have it..

As you referenced the same article I did,
http://support.microsoft.com/?id=892375, it still appears
no one has a good idea on how to automate step 1 of the
article to make it useful to be used in any managed
environment..

Thanks for the great FAQ!

|\\arco..
-----Original Message-----
I would recommend that you block it.

If you want all the options, here's my list of "useful" information for
managed environments:
(most useful may well be blocking it, perhaps allowing it to run, but
disabling real-time protection (see the workaround section of the first KB
reference)--and the unattended uninstall--for those situations where it is
already in place.

[Managed environments, scripting, turning off real-time protection]

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/a rticles/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.t xt

--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

Since there is no official support on this product, yet
people are installing it to combat the war on Spyware. I
have some questions:

Before we have issues with our domain Login Scripts and
SMS deployments, how do we automate the steps listed in
this article?

http://support.microsoft.com/?id=892375

I don't see how we can execute workaround step 1 in an
automated fashion and prohibet this problem in our
environment.

If we can't do this, we will be forced to prohibet the
installation of the AntiSpywareBeta.exe through a GPO to
keep it off our production clients worldwide.

Any thoughts?

|\\arco..
Click to expand...
Click to expand...
Click to expand...
 
Back
Top