Loading...

Knowledge Center


McAfee Agent 4.8 Patch 3 Known Issues
Technical Articles ID:   KB83733
Last Modified:  4/8/2017

Environment

McAfee Agent (MA) 4.8 Patch 3

Summary

This article contains important information about known issues of high or medium rating that are outstanding with this product release. This article will be updated if new issues are identified post-release, or if additional information becomes available. To read the Release Notes, see: PD25667.

McAfee Agent 4.8 Patch 3 is currently Released to World (RTW). This means that the product is available to all customers on the Product Downloads site at http://mcafee.com/us/downloads/downloads.aspx. For more information about release cycles, see KB51560.

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.

Release to Support (RTS): N/A
Release to World (RTW): February 17, 2015

Known Issues

CRITICAL:

 
Reference Number Related Article Issue Description
 1053371 KB84577 Issue: "Failed to obtain agent GUID" displays in the McAfee Agent for Linux log when an agent is not communicating with ePolicy Orchestrator (ePO).
Resolution: This issue is resolved in McAfee Agent 4.8 Patch 3 Hotfix 3 for Linux (Build 4.8.0.1995). See the related Knowledge Base article for details.

Non-critical:
 
Reference Number Related Article Issue Description
1113508 KB86509 Issue: McAfee Agent incorrectly reports the number of installed CPUs on systems with large numbers of physical or virtual CPUs.
Resolution: This issue will be resolved in future versions of McAfee Agent. The fix is currently targeted for McAfee Agent 4.8.4 and McAfee Agent 5.0.4. See the related Knowledge Base article for details.
1096326 KB86502 Issue: Agent communication and policy enforcement fail for McAfee Agent 4.8 after installing on Windows 10 when VirusScan Enterprise 8.8 Patch 6 is already installed.
Workaround: See the related Knowledge Base article for details.
Resolution: This issue does not occur with McAfee Agent 5.x.
  KB85870 Issue: McAfee Agent or ePO installation fails with the following error when KB3072630 is installed:
Error 1911.Could not register type library for file C:\Program Files (x86)\McAfee\Common Framework\ComponentUserInterface.dll
Workaround: Temporarily uninstall KB3072630 from Windows Updates and then re-install McAfee Agent or ePO. See the related Knowledge Base article for details.
  PD25667 Issue: The readme.html contained inside the McAfee Agent 4.8 Patch 3 package files is incorrect.
Workaround: You can ignore the readme.html contained in the package. Please refer to the posted Release Notes available for download on the Product Downloads site, and also linked at left (PD25667).
1108985 KB86193 Issue: McAfee Agent deployment fails to non-Windows systems running recent versions of ssh-server.
Workaround: Manually replace the PSCP executable that ePO uses to initiate the file transfer. See the related Knowledge Base article for details.
1025622   Issue: Total disk space and used disk space are reported incorrectly on RHEL 7 64-bit systems.
1025613  KB83993 Issue: A minor syntax error displays during installation of McAfee Agent on Ubuntu.
Resolution: This error causes no functional impact and can be safely ignored. See the related Knowledge Base article for details.
 818917   Issue: A McAfee Agent upgrade from 4.6.x is unsuccessful on some Windows XP SP3 32-bit systems when Avecto Privilege Guard is installed and a reboot has not occurred since the Privilege Guard installation.
Workaround: Avecto Privilege Guard strongly recommends a restart of the system after installation. Alternatively, restarting Avecto Privilege Guard allows a successful agent upgrade.
848114   Issue: The McAfee Agent 4.8 Help content is not available, even if the McAfee Help extension is installed on ePO 4.5 and 4.6. 
Workaround: There is a separate help extension available for ePO 4.5 and 4.6.
797382   Issue: When you compare client tasks in ePO, the output displays string IDs instead of the actual strings.
 

Rate this document

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.