Loading...

Knowledge Center


End of Life and End of Sale for Endpoint Encryption for PC 5.2.x
Technical Articles ID:  KB77999
Last Modified:  5/19/2015
Rated:


Environment

McAfee Endpoint Encryption for PC 5.2.x

Summary

This support statement is provided by the Product Management Team.

McAfee announces End of Sale (EOS) and End of Life (EOL) for Endpoint Encryption for PC (EEPC) 5.2.x.


End of Sale and End Of Life of EEPC 5.2.13, 5.2.12, and 5.2.6  (Posted: November 5, 2014)  
  • On December 31, 2014, EEPC 5.2.13, 5.2.12, and 5.2.6 will reach the EOS stage. As of this date, this product will not be available for purchase. 
     
  • On June 30, 2016, EEPC 5.2.13, 5.2.12, and 5.2.6 will reach the EOL stage. As of this date, McAfee will no longer provide technical support for these versions.     
     
End of Sale and End Of Life of EEPC 5.2.0 - 5.2.5 and 5.2.8 - 5.2.11 (Posted: March 31, 2013)
  • On March 31, 2013, EEPC 5.2.0 - 5.2.5 and 5.2.8 - 5.2.11 will reach the EOS stage. As of this date, this product will not be available for purchase.
     
  • On March 31, 2014, EEPC 5.2.0 - 5.2.5 and 5.2.8 - 5.2.11 will reach the EOL stage. As of this date, McAfee will no longer provide technical support for these versions. However, customers can still purchase and receive support for EEPC 5.2.6, 5.2.12, and later releases.
NOTE: For details about the supported Drive Encryption (DE) 7.1.x migration paths, see the DE 7.1.x supported environments article KB79422 and the FAQs article KB79784.


Migrating to ePO management and DE 7.1.x / EEPC 7.0.x
EEPC 5.2.1 and later can migrate directly to EEPC 7.0 and ePO management. As of the release of McAfee Drive Encryption (MDE) 7.1, the only legacy EEPC versions that will be supported for a direct migration will be EEPC 5.2.6 or 5.2.12 and later.

Customers requiring FIPS compliance
McAfee advises customers who require FIPS compliant products to migrate to DE 7.1.1.

NOTE: FIPS compliance does not mean FIPS certified. For FIPS certified products, read the following section.

Customers requiring FIPS certification
McAfee advises customers who require FIPS certification to migrate  to DE 7.1.1, which incorporates the McAfee Core Cryptographic Module (kernel) and McAfee Core Cryptographic Module (user) that have completed the FIPS 140-2 validation process. To view the corresponding McAfee Core Cryptographic Module (MCCM) certificates, refer to the NIST website:

Rate this document

Did this article resolve your issue?

Please provide any comments below

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms


Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.