Re: symantec antivirus can not auto update behind isa 2004

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Rick Dilley (RDilley_at_tesslerweiss.com)
Date: 09/16/04


Date: Thu, 16 Sep 2004 13:05:46 -0400

Alberto,

I believe that you did not understand Stuart's suggestion.

I have SBS2000 with ISA2000 and dual NIC configuration.

I use SSC to administer Symantec Antivirus Corporate Edition version 8.x

I have loaded SAVCE onto the SBS2K DC and told the server to obtain updates
"continuously" directly from Symantec at 60 minute intervals.

I have configured the SAVCE clients to obtain updates from MY SERVER
"continuously" at 30 minute intervals.

It was necessary to tell the server configuration to use the proxy
server(ISA) to access Symantec's Update servers.

I do not have any SAV scheduled events.
I did not have to create any ISA policies

It all works fantastically. Bandwidth is minimal. Protection is
Maximum...every desktop has an update in less than 90 minutes from
Symantec's release.

Perhaps, you might consider this scenario?

RickD

"Alberto Dallagiacoma" <Alby@Work> wrote in message
news:#7yjoO9mEHA.3296@TK2MSFTNGP10.phx.gbl...
> Hello,
> Here's how I solved the problem:
>
> 1. I created a new computer object called "Antivirus Server" with the
> corresponding IP address.
> 2. I created a domain set called "Symantec liveupdate" corresponding to
> *.symantecliveupdate.com
> 3. I created the following access rule: Action: allow, Protocols: HTTP,
> From: Antivirus Server, To: Symantec liveupdate, Users: "All Users" and
> "System and Network Service", Schedule: Always, Content: all content types
> 4. I disabled the schedule in the Symantec System Center and I scheduled
the
> liveupdate activity with a scheduled taks executing the following command:
> "C:\Program Files\SAV\VPDN_LU.exe" /silent.
> The security context of the scheduled task is NT AUTHORITY\SYSTEM
>
> HTH,
> Alberto, Italy
>
>
> "tomding" <tomding1968@163.com> ha scritto nel messaggio
> news:ugRgORsmEHA.1716@TK2MSFTNGP12.phx.gbl...
> > thanks for reply.
> > I find more people meet the problem as me.Could you describe the two
ways
> > step by step?
> > I allow all domain users to access internet by all protocols in isa 2004
> > server.
> > I scheduled LiverUPdate into Symantec System Center,but I can not
> understand
> > you saying "you have to change
> > the security context of the 'Symantec Antivirus Server' service, setting
> an
> > user that have an allow rule on the ISA Server."
> >
> > I find "Symantec AntiVirus Definition Watcher service" started by
> > localsytem,and I create an allow rule on ISA Server for the "System and
> > Network Service" group,but it does not work still.
> >
> > BTW,I find all windows os behind isa 2004 can not autoupdate as the
> > symantec. it is hard work to modify all servers and clients config
behind
> > isa 2004.so I hope to find a way in isa 2004 server to resolve all
> > autoupdate or scheduled update problems.
> >
> > "Alberto Dallagiacoma" <Alby@Work> дÈëÓʼþ
> > news:%233N9wOlmEHA.4004@TK2MSFTNGP10.phx.gbl...
> > > Hi,
> > > How didi you schedule LiveUpdate?
> > > If you created a scheduled task, you have to add an allow rule for the
> > user
> > > you assiged to the scheduled task.
> > > If you scheduled LiverUpdate into Symantec System Center, you have to
> > change
> > > the security context of the "Symantec Antivirus Server" service,
setting
> > an
> > > user that have an allow rule on the ISA Server.
> > > In the scheduled task case, you may set SYSTEM as accoutndesignated to
> run
> > > the task and create an allow rul on ISA Server for the "System and
> Network
> > > Service" group.
> > >
> > > HTH,
> > > Alberto, Italy
> > >
> > > "tomding" <tomding1968@163.com> ha scritto nel messaggio
> > > news:ePIRGohmEHA.2968@TK2MSFTNGP14.phx.gbl...
> > > > My symantec antivirus Server and clients are behind ISA 2004 stand
> > > version.I
> > > > can manually run Live Update but the scheduled updates fail with an
> > event
> > > ID
> > > > 16, saying "Download of virus definition file from LiveUpdate server
> > > failed.
> > > > 00000001." Does this have something to do with the ISA server?Do I
> need
> > to
> > > > create a custom packet filter? Or is there another issue
> > > > going on? Thanks.
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Relevant Pages

  • Re: symantec antivirus can not auto update behind isa 2004
    ... I have SBS2000 with ISA2000 and dual NIC configuration. ... I use SSC to administer Symantec Antivirus Corporate Edition version 8.x ... I have configured the SAVCE clients to obtain updates from MY SERVER ... I disabled the schedule in the Symantec System Center and I scheduled ...
    (microsoft.public.isa.enterprise)
  • Re: symantec antivirus can not auto update behind isa 2004
    ... I have SBS2000 with ISA2000 and dual NIC configuration. ... I use SSC to administer Symantec Antivirus Corporate Edition version 8.x ... I have configured the SAVCE clients to obtain updates from MY SERVER ... I disabled the schedule in the Symantec System Center and I scheduled ...
    (microsoft.public.isa)
  • Re: symantec antivirus can not auto update behind isa 2004
    ... I have SBS2000 with ISA2000 and dual NIC configuration. ... I use SSC to administer Symantec Antivirus Corporate Edition version 8.x ... I have configured the SAVCE clients to obtain updates from MY SERVER ... I disabled the schedule in the Symantec System Center and I scheduled ...
    (microsoft.public.isa.configuration)
  • Re: symantec antivirus can not auto update behind isa 2004
    ... I have SBS2000 with ISA2000 and dual NIC configuration. ... I use SSC to administer Symantec Antivirus Corporate Edition version 8.x ... I have configured the SAVCE clients to obtain updates from MY SERVER ... I disabled the schedule in the Symantec System Center and I scheduled ...
    (microsoft.public.isa.clients)
  • Re: Cant see performance report, etc. SBS2003
    ... When you install Symantec EP it adds Symantec to the web-sites in IIS. ... Reporting in server management does not work and give HTTP 404 error. ... Reinstall Monitoring component: ...
    (microsoft.public.windows.server.sbs)