Re: CA antivirus software will not update after installining ISA 2004

I don't recommend having the clients download updates directly from CA - too
much monitoring to make sure they have not stopped doing so. I do use CA's
FTP server as a backup source, particularly on laptops that don't always
have access to the SBS.

CA has a patch that lets XP SP2 boxes work over the LAN. It's a quick exe
that puts the proper exceptions in the client PC's Windows Firewall. Have
you installed that on all the workstations? If not, that would be a place
to start.

Signature file updates are not "pushed" out to the clients. By default, the
client checks with the distribution server at startup, and every X days or
hours depending on the schedule you set. You can set this manually on the
client in Scanner -> Signature update, but you should really be applying
these settings from the server (see last paragraph). I have the server
checking for updates every two hours, then the client PCs check with the
server every two hours, half an hour later than the server. (Server checks
at 2, clients check server at 2:30).

Go into the CA program on the server. Click Scanner -> Signature Update.
On the back tab, make sure you've selected for the server to be a
distribution server, hold time is 0, and that you're getting both types of
updates for XP. Click View -> Log Viewer and look at the Distribution
Events log to see if you get any help there.

Once you get that working, you can go into the admin console and define
policies that you want applied to the client PCs and/or servers, create
groups on which these policies are to be applied, schedule scans to occur
off-hours, monitor to make sure that all the workstations are updating
correctly, and view reports of scanner and virus activity, problem
workstations, etc. Check all this out and I can tell you more about it if
necessary. If you have the patch for XP, you should be able to run a
"discovery" from the admin console to see and manage all the workstations
that have eTrust installed on them.


"Jerry" <Jerry@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:583F63D9-7C98-42D5-B558-8F4659D19FD9@xxxxxxxxxxxxxxxx
>I have managed to get the CA antivirus software to download signitures to
>the
> SBS server, but the redistribution of the signitures to the clients is
> still
> not working. I cannot download virus signitures from the redistribution
> server or from CA's FTP server from the client PC's
> --
> Jerry
>
>
> "Jerry" wrote:
>
>> I just installed ISA 2004 on an SBS 2003 Premium Server and I need to
>> configure the firewall to allow my antivirus program to download virus
>> signiture updates. I assume that I have to configure an access rule, but
>> I
>> need to know the correct procedure to do it. any help would be
>> appreciated.
>> --
>> Jerry


.

Relevant Pages

  • Re: WSUS Client not yet reported
    ... The client still fails to report. ... Check your server status ... Suggestion 2: Check the IIS settings: ... any updates in your thread. ...
    (microsoft.public.windows.server.sbs)
  • Re: SUS
    ... > I have setup a SUS Server on win2k. ... 0-2.reg will not configure your machine to automatically download updates from ... critical updates or service packs that your machine needs. ... It will also ask you if you want to install them, ...
    (microsoft.public.windows.server.general)
  • Re: FYI for eTrust AV 7.x Users
    ... When I just had my little incident with the redistribution settings on the SBS, my clients were logging successful checks for updates, and the logs indicated that no updates were found. ... That turned out to be because I had not gone back and checked the redistribution server box for 8.x after reinstalling the redistribution server. ... installed the new remote install utility which works the same as v7 did - just edited the .ICF file the way I wanted it and ran the client upgrades from the server. ... I can't remember if it's a separate install, or if you have to click a box when you do the Agent install, but redistribution server is not installed by default. ...
    (microsoft.public.windows.server.sbs)
  • RE: WSUS Client not yet reported
    ... The root cause can be at either the server side or the client side. ... please check if it works with WSUS. ... any updates in your thread. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS Client not yet reported
    ... The root cause can be at either the server side or the client side. ... please check if it works with WSUS. ... any updates in your thread. ...
    (microsoft.public.windows.server.sbs)