Articoli tecnici ID:
KB88996
Ultima modifica: 10/12/2021
Ambiente
McAfee Endpoint Upgrade Assistant (EUA) 2.x
Riepilogo
Recent updates to this article
Date
Update
October 12, 2021
Added EUA 2.11 to the "Product release Information" section. Updated issues EUA-5461 and EUA-5193 as resolved in EUA 2.11.
July 29, 2021
Added issue EUA-5461 to the "Non-critical known issues" section.
May 25, 2021
Added issue EUA-5193 to the "Non-critical known issues" section.
April 14, 2021
Added EUA 2.10 to the "Product release Information" section.
March 9, 2021
Updated for EUA 2.9 Hotfix 1.
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, go to the Product Downloads site.
Issue: When you try to add the Endpoint Security (ENS) 10.6.1 Adaptive Threat Protection 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
EUA-5461
2.10
2.11
Issue: EUA Package Creator doesn't recognize ENS 10.7.0 February 2021 Update as Windows 10 21H1 compatible.
Workaround: If you use Package Creator through the command line interface, use the –ignoreensoscheck to allow this version of ENS to be used. If you use Package Creator through the graphical user interface, use the check box to avoid the operating system check. Don’t use both.
Resolution: This issue is resolved in EUA 2.11.
EUA-5193
2.9
2.11
Issue: Running Environment Analysis against many subgroups can cause an HTTP 400 Bad Request error.
Workaround: Select individual subgroups to run Environmental Analysis against.
Resolution: This issue is resolved in EUA 2.11.
EUA-3881
2.9
Issue: Downgrade of an installed EUA extension leaves the extension in a corrupt unusable state. If you want to downgrade the EUA extension, first remove it, and then install the older version.
2.7
2.8
Issue: EUA Package Creator doesn’t allow you to deselect Adaptive Threat Protection when you install ENS 10.7 or later.
Resolution: This issue is resolved in EUA 2.8.
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. This downgrade causes undefined behavior.
Workaround: Migrate to a release of ENS later than 10.5.2 to make sure that SysCore isn’t downgraded.
2.1.0
Windows Update KB3033929
Issue: If you use EUA to migrate from Windows 7, it might fail where Windows Update KB3033929 hasn’t been applied.
Resolution: Apply Windows Update KB3033929 because this update adds the required SHA256 certificate support to Windows 7 and resolves this issue.
2.0.0
Issue: After an upgrade, Data Loss Prevention requires a restart to be fully functional. If an administrator configures the agent policy for either of the following:
Show the restart dialog (Prompt user when a reboot is required) or
Force a reboot (Force automatic reboot after (seconds)
Then EAU doesn’t honor these agent policies.
Workaround: Restart the system. Data Loss Prevention is fully activated after the next system restart.
2.0.0
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.
2.0.0
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.
Issue: You use the EUA Package Creator to create an 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.
2.0.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.
2.0.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.
2.0.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.
NOTE: Any future product functionality or releases mentioned in the Knowledge Base are intended to outline our general product direction and should not be relied on, either as a commitment, or when making a purchasing decision.
