Re: FYI for eTrust AV 7.x Users



A few Q's:

1) Did you use the v8.1 CD or did you get updates from the web? With 7.1 my
CD was so old it needed upteen patches but I don't see any updates for v8.1
up on CA's site (unless I'm looking int he wrong place). Maybe with this
new update system you mention updates are obsolete...

2) Were you able to remotely upgrade the client PC's as well? I used their
remote install in 7.1 and it worked OK (other than not going through the
Windows XP firewall) and was wondering if v8.1 worked similarly.

3) So they changed it so you need a contract to get signatures? Oh well, it
was cheap while it lasted.

4) Did you uninstall the 7.1 exchange part before upgrading or does it
maintain your exclusions etc. if you install over top? I see CA doc
TEC432016 documents a bug if you install over-top but wasn't sure if it
applies.

5) Do you know of any issues running it on a terminal server?


Thanks.

--
Allan Williams



"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23ug$yeKXJHA.1184@xxxxxxxxxxxxxxxxxxxxxxx
I can't really say that Apache has caused me any problems. It runs two
services, and eTrust runs five. Probably using about 100 MB of RAM or so
on the server. The interface, changing settings, etc. definitely performs
noticeably slower than 7.x, although it doesn't seem to have much more
impact on the workstations.

Version 8 enforces licensing, so you need to be sure that all the
workstations are properly licensed. Otherwise, the default is a 30 day
trial license, and they'll stop getting signature updates at that point.
There's a thing called "phone home" that you can configure to point to the
SBS (assuming that's where the server part of eTrust is installed). Then
you set the phone home schedule to "disabled," and somehow that makes it
pick up the license from the server install. (This licensing thing is
because you now need to be under a paid support contract in order to get
signature updates).

The best thing about it is that all the parts are upgraded through the
regular distribution, not just signature files. So if there's a driver
update or other part that gets a new version, it'll be installed
automatically when the signatures update.

Also, Exchange is a separate install. If you just run the eTrust
installer once to update the server install, it'll leave Exchange at 7.x.
You have to run the installer a second time to upgrade Exchange.

Let me know if you have questions - I've probably messed with this enough
by now that I might be able to help at least a little.


"Al Williams" <donotreplydirect@xxxxxxxxxxxxxxxx> wrote in message
news:et2F9JJXJHA.5272@xxxxxxxxxxxxxxxxxxxxxxx
Still using CA 7.1 on our SBS 2003 Sp2 Premium - always liked CA because
it works well (once configured which can be a pain) and is cheap to
maintain (no service contract needed for updates).

Was planning on moving to v8.1 in the near future. What sort of issues
do you know of and any tips appreciated. I wasn't aware of the Apache
thing does that cause issues?

--
Allan Williams



"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:%23M%23mxk%23WJHA.868@xxxxxxxxxxxxxxxxxxxxxxx
I doubt there are many SBS'ers using eTrust antivirus, but I'll mention
this just in case. Apparently the 7.x versions are going off support on
December 31, including that the signature files will no longer be
updated. If you're using one of these, you'll have to upgrade to the
newer version or a different product by then. I can comment on version 8
if anyone is interested - it installs Apache on the server, which may be
a deal breaker for some all by itself.

https://support.ca.com/irj/portal/anonymous/phpsupcontent?contentID=172833&productID=156





.



Relevant Pages

  • 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: Disaster Restore SBS2003
    ... If you had the server set to download updates automatically (never ... then install any service packs to return the server to the same service pack ... have the correct version of NTBackup prior to the restore. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... the old array was a raid 5 that should not have become so rooted but the twit who built the server did not actually enable the spare drive to act as a spare!! ... The problem is SBS is unique and I've rarely if ever seen it work. ... The server has been chugging away in a small business environment for several years and I have administered it for them for about a year making sure that the updates were installed and their mailboxes were managed etc etc. ... My main reason for slipstreaming the install is because I cannot get the original 2003 server install to cope with the new hardware and it falls over part way into the install - BSOD bit. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)

Loading