Exporting Spyware settings

  • Thread starter Thread starter Tim
  • Start date Start date
T

Tim

Using the /a switch I installed the MS Antispyware
software to a network share, then used Group Policy to
assign the app to a few test workstations. This worked
fine except for the critical error 101 issue, which I
fixed with help from this forum. What I would like to do
now is export the settings from my pilot workstation to
the others in the test group. Stuff like schedule
settings etc.

Is this info stored in a particular file or registry hive?
Is it possible to export this sort of info, or would this
sort of functionality only be available with the
Enterprise version?
 
There are posts in the .install group relating to this issue, but there's
nothing solid, so I'll repeat it.

The only method I've heard which seems to hold promise--and I believe
there's one post from a user who tried it with success--is to make the
changes you wish to a clean install, observe which .GCD file(s) in the
installation folder under program files changed, and plop those files down
on the workstations (plop is a technical term--I can't tell you how to do
this properly, but I don't think it is too hard!)

This is a kluge, is ugly, and may easily change at some point in the beta or
not be transferrable to the final product, but it is a way to try to do what
you are interested in.

For the record: This beta product really isn't suitable for this usage.
Among the issues are:

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

A future managed, Enterprise-suitable version, which Microsoft has announced
will be available, should be appropriate--but no timing or beta availability
has been announced for such a product.
 
Just to reiterate here - attempts to install with the MSI file in policy can
have varying results. You are almost guaranteed a 101 error when you attempt
to deploy the beta this way. The only way to deploy the beta is by going to
each machine and installing from the web.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
Back
Top