Re: FYI for eTrust AV 7.x Users

1. I had a bad experience trying to install this from a download when we got the first Vista box a year or so ago, and had to reinstall it from the CD. Since then, I've done all the rest from the CD. Either way, the updating thing does seem to make it less relevant as long as you get some version of 8.1. It'll be current after the first download either way.

2. I want to touch each PC anyway, to make sure the licensing is configured properly. So, I have not tried the remote install. I'm just doing them individually as time allows, since all the XP boxes are doing fine with version 7. When I renewed the license last, I had one Vista desktop that failed to pick up the renewal and stopped updating, so I want to see that none of the desktops are showing the trial license.

3. You do need a contract to get signatures now - as far as I know, it's the regular CA thing that includes support, software updates, etc. If I remember right, it costs in the neighborhood of $12 per seat per year, including the server and Exchange. If you don't have a CA open license vendor, try SoftwareONE. I get my MS open licenses from them too - they're great.

4. I've done all in-place upgrades. I did the console first (the 8 console works with 7, but the 7 console does not work with 8). Once the console was done, I did the Vista boxes as I deployed them (7 doesn't work on Vista). Now I've been doing the XP boxes one or two at a time until I get them all upgraded. In-place upgrade retains your existing settings (if you choose the option). However, for settings that don't exist in 7, they'll be at the defaults. That means in particular, the "phone home" feature will not be configured. That's what gets you the licensing from the SBS, so you need to make sure that's done. You can control that setting from the console, but if you do that without verifying that the setting applied correctly, you'll need to monitor that the desktops don't fail to update after the expiration of the trial license.

5. Have not tried it on a TS, but I can't see any reason it wouldn't work as expected.



"Al Williams" <donotreplydirect@xxxxxxxxxxxxxxxx> wrote in message news:OZ7HV0KXJHA.5272@xxxxxxxxxxxxxxxxxxxxxxx
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: upgrade XP home to XP pro
    ... How do I put XP pro onto the inherited machine? ... Will it upgrade if I insert the XP Pro disk and run the install program or must I reformat the hard drive on the inherited machine? ... An OEM license is permanently bound to the computer on which it was originally installed, and may never be legitimately transferred to a new computer. ... WinXP is designed to install and upgrade the existing operating system while simultaneously preserving your applications and data, and translating as many personalized settings as possible. ...
    (microsoft.public.windowsxp.newusers)
  • Re: Reverting to XP from Vista
    ... Let me elaborate on the rumor that an upgrade edition of Vista invalidates the XP license already installed on the machine. ... You can do an upgrade or custom install on 1 but only a custom install on 2. ...
    (microsoft.public.windowsxp.general)
  • Re: KB898458???
    ... the upgrade advisor has not even ran. ... Insert the XP disk. ... Immediately install SP2: ... Make certain Automatic Updates is enabled. ...
    (microsoft.public.windowsxp.general)
  • Re: 800703E7 error message
    ... I get this message when trying to install service pack 2. ... > Check for hardware driver updates? ... > Patches and Updates! ... > drivers for your hardware/operating system. ...
    (microsoft.public.windowsupdate)
  • Activation Key Question
    ... old ME disk and license). ... the old retired machine on the new install on the new machine (the install ... then it hit me that I was attempting to use an upgrade key. ...
    (microsoft.public.windowsxp.setup_deployment)
Loading