E
Edwin Davidson
I installed XP SP2 onto a test XP station. Although it recognized
eTrust antivirus 7.0, it broke it as well.
The station could no longer get antivirus pattern updates over FTP.
The XP firewall log showed that the XP firewall was blocking the FTP
connections being made by eTrust to update its' pattern files.
I checked on esupport.ca.com, and sure enough CA knows that there are
problems with eTrust and XP SP2.
The problem I have is all the laptops that are all over the world,
that are configured to use Automatic updates, that will get SP2 and
will no longer be getting antivirus updates.
The users will not complain, because they don't see anything wrong.
Getting all of these folks in so we can install SP2, and then install
the eTrust patches (which must be installed AFTER SP2 is installed.)
is going to cost us a lot of money.
My question is this: Why does XP SP2 recognize eTrust antivirus is
installed and subsequently prohibit it from updating the antivirus
patterns?
While I am making provisions to handle this, I know that thousands of
XP/CA customers will not have the resources to address this issue and
thus they will be scr*d over by another Microsoft *feature* (patch)
that breaks things. (The firewall isn't going to block e-mail/http
born viruses.)
Am I mistaken?
Edwin Davidson.
eTrust antivirus 7.0, it broke it as well.
The station could no longer get antivirus pattern updates over FTP.
The XP firewall log showed that the XP firewall was blocking the FTP
connections being made by eTrust to update its' pattern files.
I checked on esupport.ca.com, and sure enough CA knows that there are
problems with eTrust and XP SP2.
The problem I have is all the laptops that are all over the world,
that are configured to use Automatic updates, that will get SP2 and
will no longer be getting antivirus updates.
The users will not complain, because they don't see anything wrong.
Getting all of these folks in so we can install SP2, and then install
the eTrust patches (which must be installed AFTER SP2 is installed.)
is going to cost us a lot of money.
My question is this: Why does XP SP2 recognize eTrust antivirus is
installed and subsequently prohibit it from updating the antivirus
patterns?
While I am making provisions to handle this, I know that thousands of
XP/CA customers will not have the resources to address this issue and
thus they will be scr*d over by another Microsoft *feature* (patch)
that breaks things. (The firewall isn't going to block e-mail/http
born viruses.)
Am I mistaken?
Edwin Davidson.