Central updates

[Oliver Maynard]

Hi,

I am using antispyware in a school on multiple clients and
wondered if there is a way to centrally deploy the updates
as they are released. It would be a much better way to
ensure the updates take place.

Many Thanks

 

[JohnF.]

I am sure when MS releases the enterprise version of this tool, that will be
part of the package. For now, you are using a beta that is meant to be
standalone and only functioning on admin access level accounts. You could
write a script to copy the appropriate files to the appropriate locations
but you just might break something too.

 

[Bill Sanderson]

I agree with all of JohnF's remarks. Here's a kb article showing what files
are involved, fwiw.

http://support.microsoft.com/default.aspx?scid=kb;en-us;892519

 

[Guest]

We are more than happy to write scripts, make local DNS
changes to make a local update work... HOWEVER there is a
notable lack of documentation for where the files are and
where they go! How's about a little disclosure here boys?

Ken
Shelby County Board of Ed.

 

[Bill Sanderson]

Did you notice that I've published the kb link showing the files involved to
this thread, before your posting?

This is a beta product. Many things may change before it is released. If
something is not documented, I wouldn't recommend building any substantial
processes on the assumption that it won't change.

 

[Guest]

This tells how to verify the version of the library, but
does not help in what I'm looking for. Which is simply
this.
1. Where are the update libraries available to download.
2. (Will prob know when I have them but) Where do they
need to be placed on a workstation.

What I would like to accomplish is an update process that
doesn't involove any user touching the software. Simply
copy files when the user logs into the network.

While that may seem antiquated, it would satisfy my needs
until such time as MS has this working with SUS.

Ken

 

[Robin Walker [MVP]]

1. Where are the update libraries available to download.

They are not available for download. They can only be downloaded as part of
the normal operation of MSAS's self-update process.

2. Where do they need to be placed on a workstation.

In the same place as they are in any already working installation of MSAS.

What I would like to accomplish is an update process that
doesn't involove any user touching the software. Simply
copy files when the user logs into the network.

Unless your network users operate with full local administrative access,
this is not going to work. MSAS (in this beta release) works only for
stand-alone systems with users having full Administrator rights. MSAS also
interferes with some operations that occur during a domain logon, enabling
your users to defeat any constraints you might have placed on them as part
of their network configuration.

Besides, MSAS is auto-updating, and deos not require you to provide a
further update process. If you provide your users with MSAS, it will keep
itself auto-updated.

 

[Beyondtool]

The issues here are more related to bandwith than the fact
that MS Antispyware keeps itself up to date.

I'm wondering how to manage these updates in a large user
environment with a small internet pipe. We do have a
proxy server, but that's only going to save us if the
machines don't update at the same time. Is it going to be
difficult to set one machine to update automatically
before the others so the proxy server can cache the
update?

Our users are currently in the Interactive gorup which
grants them limited admin rights, will I still have
problems with MS Anitspy interfering with Group Policy or
domain logon? What kind of problems have people
experienced?

-----Original Message-----

1. Where are the update libraries available to download.

They are not available for download. They can only be downloaded as part of
the normal operation of MSAS's self-update process.

2. Where do they need to be placed on a workstation.

In the same place as they are in any already working installation of MSAS.

What I would like to accomplish is an update process that
doesn't involove any user touching the software. Simply
copy files when the user logs into the network.

Unless your network users operate with full local administrative access,
this is not going to work. MSAS (in this beta release) works only for
stand-alone systems with users having full Administrator rights. MSAS also
interferes with some operations that occur during a domain logon, enabling
your users to defeat any constraints you might have placed on them as part
of their network configuration.

Besides, MSAS is auto-updating, and deos not require you to provide a
further update process. If you provide your users with MSAS, it will keep
itself auto-updated.

--
Robin Walker [MVP Networking]
(e-mail address removed)


.

 

[JohnF.]

The proxy server will queue all the requests even if they seem to be all at
the same time. The first request will fetch the update, the rest will use
the cached file.

The issues here are more related to bandwith than the fact
that MS Antispyware keeps itself up to date.

I'm wondering how to manage these updates in a large user
environment with a small internet pipe. We do have a
proxy server, but that's only going to save us if the
machines don't update at the same time. Is it going to be
difficult to set one machine to update automatically
before the others so the proxy server can cache the
update?

Our users are currently in the Interactive gorup which
grants them limited admin rights, will I still have
problems with MS Anitspy interfering with Group Policy or
domain logon? What kind of problems have people
experienced?

-----Original Message-----

1. Where are the update libraries available to download.

They are not available for download. They can only be downloaded as part of
the normal operation of MSAS's self-update process.

2. Where do they need to be placed on a workstation.

In the same place as they are in any already working installation of MSAS.

What I would like to accomplish is an update process that
doesn't involove any user touching the software. Simply
copy files when the user logs into the network.

Unless your network users operate with full local administrative access,
this is not going to work. MSAS (in this beta release) works only for
stand-alone systems with users having full Administrator rights. MSAS also
interferes with some operations that occur during a domain logon, enabling
your users to defeat any constraints you might have placed on them as part
of their network configuration.

Besides, MSAS is auto-updating, and deos not require you to provide a
further update process. If you provide your users with MSAS, it will keep
itself auto-updated.

--
Robin Walker [MVP Networking]
(e-mail address removed)


.

 

[Bill Sanderson]

The issues here are more related to bandwith than the fact
that MS Antispyware keeps itself up to date.
Our users are currently in the Interactive gorup which
grants them limited admin rights, will I still have
problems with MS Anitspy interfering with Group Policy or
domain logon? What kind of problems have people
experienced?

In the current beta build, and the refresh update available before July 31,
I don't expect what you mention above to change. I would expect it to
change eventually, but I'm not at all sure when. Surely a change to
available Group Policy settings will take something more than a simple app
release to accomplish?