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: [EMAIL PROTECTED] > 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 >
