Re: [foxboro] Virus protection

  • From: Terry Doucet <doucet427@xxxxxxxxxxx>
  • To: <foxboro@xxxxxxxxxxxxx>
  • Date: Wed, 28 Apr 2010 23:20:33 -0400

For my own virus-scan software, not McAfee, I bought the product which licenses 
me to run the program on three computers. Each year I have to buy a licence 
which allows me to get updates for the virus definition files. If I do not pay 
the fee, I can still run the virus scan program with the old definition files 
(for whatever good that might do).

 

So you need to know what license you have for the virus scan program and 
howmany processors it can run on. Then you need to know the cost to be 
permitted to download the definition files. Of course all this must meet with 
Foxboro / Invensys approval to run on an AW processor.

My experience was that McAfee was a bit of a pig - cpu wise. Even if you 
throttled it down to 10% max, it could still cause AW problems. So we used to 
scan the whole drive(s) after installation before the AW got busy, then we 
never scanned again while the AW was working. It would scan data on access so 
that floppies and memory stiks got scanned before processing.

Terry
 
> Subject: Re: [foxboro] Virus protection
> Date: Wed, 28 Apr 2010 16:19:13 -0500
> From: Jack.Easley@xxxxxxxxxxxx
> To: foxboro@xxxxxxxxxxxxx
> 
> Yes, I think a lot of Foxboro customers are going to be surprised by
> this one. I was unaware we were running unlicensed versions of McAfee
> until recently. I'm sure the original install by Foxboro was legal, but
> these licenses have probably long expired. As you said, I assumed this
> was the same as everything else in the past from Foxboro.
> 
> McAfee requires annual license fees. If you were a home customer, your
> software would probably stop working, but apparently it does not for
> this Enterprise version. Apparently licensing for McAfee VirusScan
> Enterprise uses the honor system, but all of company's ethics policies
> require us to honor this.
> 
> When I attempted to upgrade our defunct McAfee VirusScan 8.0i recently
> with McAfee VirusScan 8.7i, I was told by a McAfee agent that
> Invensys/Foxboro has not renewed a license since 2001 and my software
> was not currently licensed, so I could not upgrade it. I had to buy
> completely new software, instead of a cheaper upgrade. And yes, all
> versions of McAfee do require annual license renewals unless you
> specifically buy 2-3-4 year licenses if you want to stay legal.
> 
> Alex...maybe you (or someone you know) can better inform us of the hard
> facts concerning Foxboro McAfee licensing and the exact details as to
> the customer's responsibility for it after the box is delivered. I'm
> hoping I'm wrong about everything above (in which case I apologize in
> advance) and Foxboro has some super-duper McAfee license that never
> expires. Foxboro also needs to at least make this fact known to their
> customers when they install new equipment, if not when they sell it.
> 
> Concerning the Symantec Backup Exec license issue, I hope it is required
> only if you want to receive Symantec hardware updates such that you
> might be able to use their "Restore Anyware" function for dissimilar
> hard-ware restores. (Never had any luck with that anyway, but I do love
> Symantec Backup Exec) That's my stand on Symantec until proven
> otherwise.
> 
> Jack Easley
> Sr. I&C Technician
> Luminant Power, Martin Lake Plant
> Phone 903.836.6273
> jack.easley@xxxxxxxxxxxx 
> 
> 
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of stan
> Sent: Wednesday, April 28, 2010 2:27 PM
> To: Foxboro List
> Subject: [foxboro] Virus protection
> 
> WE have been informed by our Foxboro sales rep that we need to sign up
> for
> support contracts with McAfee, and Synaptic to get updated copies of
> their
> software on our Foxboro machines.
> 
> I was under the impression that this software had to be blessed by
> Foxboro
> for installing on IA machines. This would make co-ordinating the new
> vendor
> releases of software with Foxboro problematic in my opinion. I had
> assumed
> that this would be covered by our Foxboro support contract.
> 
> What has been other peoples experience here? Has anyone established
> separate support contracts with either of these vendors? If so, how does
> this co-ordination work for you?
> 
> 
> 
> Confidentiality Notice: This email message, including any attachments, 
> contains or may contain confidential information intended only for the 
> addressee. If you are not an intended recipient of this message, be 
> advised that any reading, dissemination, forwarding, printing, copying
> or other use of this message or its attachments is strictly prohibited. If
> you have received this message in error, please notify the sender 
> immediately by reply message and delete this email message and any
> attachments from your system. 
> 
> 
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
> 
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 
                                          
_________________________________________________________________
Videos that have everyone talking! Now also in HD!
http://go.microsoft.com/?linkid?24465
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 

Other related posts: