Anyone reading what I said must think I've gone crazy.  I mean 6/12/2006
rev 25 definitions.  Very sorry, the day of the month jumbled with the
revision
in my mind.

----
Stefanie Ploof
CIT Client Services
CALS Information Technology Office
University of Vermont, Burlington

On Mon, 12 Jun 2006, Stefanie Ploof wrote:

> For anyone not on the IT-DISCUSS list, please note the following.
>
> ----
> Stefanie Ploof
> CIT Client Services
> CALS Information Technology Office
> University of Vermont, Burlington
>
> ---------- Forwarded message ----------
> Date: Mon, 12 Jun 2006 13:25:25 -0400
> From: Stefanie Ploof <[log in to unmask]>
> Reply-To: Technology Discussion at UVM <[log in to unmask]>
> To: [log in to unmask]
> Subject: Re: [IT-DISCUSS] "New Norton" and Trojan.Dropper
>
> I spoke with a Symantec technician who just now confirmed that other
> locations were reporting the same problem.  Rapid release definitions were
> created by Symantec to resolve the problem.  I have installed those rapid
> release definitions on the central servers, and those definitions are
> pushing out to centrally managed client machines.  When a computer has
> virus definitions 6/25/2006 rev 25 the computer should stop detecting our
> SAV installers as Trojan.Dropper.
>
> If you do not know how to check your virus definitions please read this
> document:
>
> http://www.uvm.edu/antivirus/?Page=faqs/savdefcheck.html
>
> (Please note that the current screen snapshot doesn't list a parent
> server.  I'll take another snapshot so that this isn't confusing for the
> future!)
>
> Right now the machine I have access to has stopped detecting the
> executeables as a Trojan, but I would like confirmation from others.
> Thanks, everyone!
>
> Stef
> ----
> Stefanie Ploof
> CIT Client Services
> CALS Information Technology Office
> University of Vermont, Burlington
>
> On Mon, 12 Jun 2006, Henrietta Menzies wrote:
>
> > I second  that I have had Sav version 10.1.0.401 installed for a few
> > days now and have had no issues. It doesn't seem like the new version is
> > the problem but like Jonathan suggests it is the newer definition files.
> >
> > Henrie
> >
> > Henrietta Menzies
> > Technical Support Specialist
> > Desktop & User Support
> > Residential Life
> > Robinson Hall Rm 301E
> > 656-7937
> >
> >
> > Free to Be Advisor
> > http://www.uvm.edu/~free2b
> >
> > "It is hard to belive at times but everything does happen for a reason...and even harder to figure out your place in all of it!"
> >
> >
> >
> >
> > Jonathan L. Trigaux wrote:
> > > Based on what I've observed on client computers and comments to this list,
> > > my guess is that this is an issue with current definition files and not
> > > the version of the scanning engine.  I've been seeing the previous version
> > > (10.0.2.2020) detecting Trojan.Dropper as well, so I don't think the new
> > > version upgrade announced last week (10.1.0.401) is to blame.
> > >
> > > -JLT
> > >
> > > --------------------------------------------------------------------------
> > > Jonathan L. Trigaux
> > > CIT Client Services | Rubenstein School of Environment & Natural Resources
> > > 111 Waterman | 342 Aiken
> > > University of Vermont
> > > Burlington, VT 05405
> > >
> >
>