Loading...

Knowledge Center


Endpoint Upgrade Assistant Known Issues
Technical Articles ID:   KB88996
Last Modified:  10/8/2019
Rated:


Environment

McAfee Endpoint Upgrade Assistant (EUA) 2.x, 1.x

Summary

Recent updates to this article
Date Update
October 8, 2019 Updated for EUA 2.5.
September 6, 2019 Minor formatting change; no content changes.
July 2, 2019 Updated for EUA 2.4.1.12. Updated issue 1274575 in the "Critical known issues" section as resolved in EUA 2.4.1.12.
June 11, 2019 Added issue 1274575 to the "Critical known issues" section.
April 9, 2019 Updated for EUA 2.4.0.126. Added issue 1266492 to the "Non-critical known issues" section.

To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.

Contents
Click to expand the section you want to view:

Issue resolutions in updates and major releases are cumulative; Technical Support recommends that you install the latest version. To find the most recent release for your product, visit the Product Downloads site at http://www.mcafee.com/us/downloads/downloads.aspx.
 
EUA Version General Availability (GA) Release Notes
2.5 October 8, 2019 Release Notes
2.4.1.12 July 2, 2019 PD28414
2.4.0.126 April 9, 2019 PD28293
2.3.1.17 November 13, 2018 PD27996
2.3.0.23 October 3, 2018 PD27992
2.2.0.23 August 7, 2018 PD27913
2.1.0.36 June 12, 2018 PD27739
2.0.0.33 April 24, 2018 PD27562
1.6.0.129 March 8, 2018 PD27478
1.6.0.121 February 14, 2018 PD27478
1.6.0.115 February 1, 2018 PD27478
1.5.0.142 November 27, 2017 PD27386
1.5.0 October 30, 2017 PD27302
1.4.0 August 14, 2017 PD27219
1.3.1 May 25, 2017 PD27094
1.3.0 April 12, 2017 PD26983

Back to top
 
Reference Number Related Article Found in EUA Version Resolved in EUA Version Issue Description
1274575   2.4.0.126 2.4.1.12 Issue: When you try to add the Endpoint Security 10.6.1 ATP May Update package to EUA Package Creator 2.4.0.126, it fails with the following error:
 
ERROR: The Update version does not match the Base version
 
Resolution: This issue is resolved in EUA 2.4.1.12.

Reference Number Related Article Found in EUA Version Resolved in EUA Version Issue Description
1266492   2.3.1 2.4.0.126 Issue: If you use EUA to migrate to Endpoint Security when only VirusScan Enterprise or Host Intrusion Prevention are installed, installation of Endpoint Security might fail.

Resolution: This issue is resolved in EUA 2.4.0.126.
    2.1.0 ENS later than 10.5.3 Issue: When you use EUA to migrate from VirusScan Enterprise 8.8 or Host Intrusion Prevention 8.0 Update 10 or 11, to Endpoint Security (ENS) 10.5.2, it results in a SysCore downgrade, which causes undefined behavior.

Workaround: Migrate to a release of ENS later than 10.5.2 to ensure that SysCore is not downgraded.
    2.1.0 Windows Update KB3033929 Issue: If you use EUA to migrate from Windows 7, it might fail where Windows Update KB3033929 has not been applied.

Resolution: Apply Windows Update KB3033929 because this update adds the required SHA256 certificate support to Windows 7 and resolves this issue.
    1.6.0.115   Issue: After an upgrade, Data Loss Prevention requires a restart to be fully functional. If an administrator configures the agent policy to show the restart dialog (Prompt user when a reboot is required) or force a reboot (Force automatic reboot after (seconds), EAU does not honor these agent policies.

Workaround: Restart the system. Data Loss Prevention is fully activated after the next system restart.
    1.6.0.115   Issue: If an upgrade from Data Loss Prevention 10 to Data Loss Prevention 11 fails, EUA reports the upgrade as a success. This report is because the same Data Loss Prevention product code is used for Data Loss Prevention 10 and 11.

NOTE: Data Loss Prevention 10 is expected to still be functional.
    1.5.0.142   Issue: All Endpoint Security versions are added to the "Upgrade complete" category. For example, if you select Endpoint Security 10.5.3 to analyze in your environment, you expect only the Endpoint Security 10.5.3 versions found in your environment to show up in the "Upgrade complete" category. Instead all Endpoint Security versions show up.
1214357 KB90036 1.5.0   Issue: You use the EUA Package Creator to create an ePolicy Orchestrator (ePO) deployable package and select the Endpoint Security 10.5.3 standalone installation package. When you try to check in the ZIP package to the ePO Master Repository, the operation fails and you receive the following error:
 
ERR_CONNECTION_RESET
 
After you refresh the page, you receive the following error:
 
You are not authorized for this operation

Workaround: Increase the package size limitations for ePO. See the related article for more information.
    1.5.0   Issue: The EUA ePO Extension accepts Data Loss Prevention Endpoint 9.3 Update 5 and later, but the EUA Package Creator accepts only Data Loss Prevention Endpoint 9.3 Update 6 or later.
    1.5.0   Issue: EUA states that it only upgrades to versions of Data Loss Prevention Endpoint that are incompatible with Endpoint Security, to Data Loss Prevention Endpoint 9.3 Update 6 or later. But, the EAU Package Creator allows you to upgrade to any Data Loss Prevention Endpoint version. For example, if an administrator creates a package that contains Data Loss Prevention Endpoint 10, Data Loss Prevention Endpoint upgrades to that version.
    1.5.0 Endpoint Security 10.6.0 Issue: Some Endpoint Security 10.5.x update packages appear as 10.5.0.xxx packages in the ePO Software Manager. The EUA "Prepare" tab displays these packages as 10.5.0.xxx version packages.

Workaround: The actual package version as displayed in ePO Software Manager is in parentheses. For example, "McAfee Endpoint Security – Platform" shows the version number as 10.5.3 and the build version number is in parentheses (10.5.0.2072).

Resolution: This issue is resolved in Endpoint Security 10.6.0.

Back to top

Rate this document

Glossary of Technical Terms


 Highlight Glossary Terms

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