McAfee agent 4.5 Patch 3 for non-windows released

McAfee Agent 4.5.0 Patch 3 Non-Windows packages are now available for download from the McAfee ServicePortal (https://mysupport.mcafee.com) and McAfee Download site (http://www.mcafee.com/us/downloads).

For full details, see KnowledgeBase Article KB72074:

Documented Known Issues

CRITICAL: None at this time

Issue
Reference
Article Descriptions
Issue:
Resolution:


Non-critical:

Issue
Reference
Article Descriptions
465069 KB67044 Issue: Non Windows installation fails with ‘Error: Could not find key data’.

Resolution:
Copy the install.sh using binary to the target machine. Refer to the KnowledgeBase article for detailed information.
311678 KB69449 Issue: Non Windows installation fails when /opt is a symbolic link.

Resolution:
Non Windows installations do not currently support or allow installation when the /opt directory is a symbolic link. Refer to the KnowledgeBase article for detailed information.
530859 KB67496 Issue: McAfee Agent 4.5 custom properties do not report to ePO 4.0 server.

Resolution: The McAfee Agent 4.5 custom property feature is designed to work only with ePO 4.5. Refer to the KnowledgeBase article for more details.

529526 KB67385 Issue: The examples provided on page 28 of the McAfee Agent 4.5 Product Guide (PD22236) and page 81 of the ePO 4.5 Product Guide (PD21812) contain a missing character, causing the installation command to fail.Resolution: Refer to the KnowledgeBase article for more details.
488282 KB66138 Issue: McAfee Agent command line option ./msaconfig -CustomProps# is not populating the lastprop.xml correctly.

Workaround:
Use the fields in sequential order.
488647 KB67018 Issue: Agent communication fails after reinstalling ePO.

Resolution:
Follow correct reinstallation steps.  Refer to the KnowledgeBase article for more details.
496122 KB67020 Issue: The first Agent-to-Server Communication Interval (ASCI) receives new sitelist policy along with an update task. The sitelist gets sorted and the sitecache.bin file is created. After completion of update task, ASCI was initiated, which also sorted the sitelist and regenerated the sitecache.bin file.

Resolution:
Refer to the KnowledgeBase article for more details.

 

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.