RE: Symantec Corporate AntiVirus 8.0 - thoughts

From: Chris Santerre (csanterre@MerchantsOverseas.com)
Date: 11/07/02 

From: Chris Santerre <csanterre@MerchantsOverseas.com>
To: 'Scott Plumlee' <scott@plumlee.org>, security-basics@securityfocus.com
Date: Thu, 7 Nov 2002 10:24:42 -0500

I've been using it for a while, and have investigated ways of handling the
updates of workstations. My situation is I don't have time to get very
fancy. I've got too many things to do, so I need it quick and easy. With
that said, here is what I do:

Every Friday, download the update definitions to a public directory and
uncompress. Run a script that renames standard user login scripts. These new
login scripts copy the virus update files to the "incoming" directory on the
clients. HUGE message in notepad opens on clients machine to tell them to
double click the little NAV icon and check the date of their definitions.
Done.

Come Tuesday morning I change the scripts back over.

There was an article on creating your own local liveupdate server. But it
was more time consuming and still felt like PULL. I wanted to PUSH the
update like this.

This is a undocumented way of updating that I stumbled on while playing one
day. So your mileage may vary.

Chris
Go Patriots!

> -----Original Message-----
> From: Scott Plumlee [mailto:scott@plumlee.org]
> Sent: Wednesday, November 06, 2002 9:13 AM
> To: security-basics@securityfocus.com
> Subject: Symantec Corporate AntiVirus 8.0 - thoughts
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Anyone have any opinions on this for managing workstation virus
> checkers? Doing it by myself and trusting the users to update is
> getting tedious. I'm interested in anyone running it on a Novell
> network especially. What do each of the modules provide that you
> like/don't like?
>
> Windows client
> Netware server package
> System center
> MMC snap ins
> Rollout tool
> etc..
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
>
> iQA/AwUBPckjSS7xgTzdLHYCEQJcCwCfcE2YtEcb4smM3tNqhN29zyi2/aEAoIm/
> ExkHdIxAuogfz1n7rajiDcyQ
> =TJPU
> -----END PGP SIGNATURE-----
>
> Scott Plumlee
> PGP Public key: http://plumlee.org/pgp/ C23E 2672 FF08 62EA
> 0796 24CD
> 2EF1 813C DD2C 7602
>

Relevant Pages

  • RE: Symantec Corporate AntiVirus 8.0 - thoughts
    ... >updates of workstations. ... Run a script that renames standard user login scripts. ... HUGE message in notepad opens on clients ... BUILT-IN, you just have to set up the Live Update Server, and configure the ...
    (Security-Basics)
  • Re: Sudden Issues with DHCP & Remote Access
    ... function and when i went to run the wizard, found that the server could not ... In one fix there were instructions to change the path of the clientapps ... then re-run CEICW and reboot the workstations. ... will be assigned to dial in clients. ...
    (microsoft.public.windows.server.sbs)
  • Re: Promted for username & password when accessing network folder
    ... logons or security / access permitions? ... workstations are joined to the same domain. ... was that some users can connect to the shared folders from certain machines, ... Are you running any login scripts or client policies on your DC? ...
    (microsoft.public.windowsxp.network_web)
  • Re: SBS 2003 no client internet access
    ... How would he go about un-joining the workstations from the domain? ... >>>You said the SBS is only used as a File and Printer server. ... >> I have replaced the clients with XP Pro clients, ... >> Internet firewall from the client.. ...
    (microsoft.public.windows.server.sbs)
  • Re: 5 access 2000 users and 1 AccessXP user
    ... Check the permissions of the folder where the workstations are connected ... > I, too, have a split database with the backend on a server. ... > started upgrading my win2K clients to XP and the server is still running ...
    (microsoft.public.access.conversion)