This release was developed for use with: McAfee ePolicy Orchestrator 3.6.1 McAfee ePolicy Orchestrator 4.0.0 McAfee ProtectionPilot 1.5
Make sure you have installed the correct version(s) before using this release.
This document supplements the Common Management Agent 3.6.0 Readme file in the release package, and details fixes included in Common Management Agent 3.6.0 Patch releases.
Issues that are resolved in this release are listed below.
1. Issue:*Systems with 16 or more processors (physical or virtual) would display the message "FrameworkService.exe - Application Error: The instruction at*‘0x7c8396d0’ referenced memory at*‘0x00000014’. The memory could not be read." (Reference: 336312)
Resolution: The Listen Server was updated to properly manage systems with 16 or more processors.
2. Issue: The Common Management Agent installation might fail due to the cleanup process being reported as "in use." (Reference: 349208)
Resolution: The Common Management Agent installation process was updated to*wait 30 seconds rather than indefinitely for the cleanup process to be completed, allowing the installation to succeed.
3. Issue: The Framework Service*blocked access to a system’s COM1 port after a compliance scan was performed. (Reference: 351166)
Resolution: The Listen Server was updated to properly respond to external queries of the ports it is using.
4. Issue: The message "The update task will be re-tried in 3 minutes because update is in progress." appeared repeatedly in the system’s Agent log, and the system was not updated to the latest DAT file. (Reference: 360487)
Resolution:*The replication process of the Common Management Agent was updated to properly manage FTP timeouts.
5. Issue:*When the Common Management Agent encountered an error querying the system’s network information, an exception occurred and the system was not updated to the latest DAT file. (Reference: 387427)
Resolution:*The Common Management Agent was updated to properly manage the ability to acquire a system’s MAC address.
6. Issue:*The Common Management Agent could generate a "Structured Exception" during periods of heavy network activity in environments using Super Agent Repositories, and the system would not get updated to the latest DAT. (Reference: 359248, 383545, 389097, 402750)
Resolution:*The network management process of the Common Management Agent was updated to better manage its network objects.
7. Issue: The Common Management Agent could generate a "Structured Exception" when an error occurred during*new policy compilation. The system would not communicate with the server until the Common Management Agent was restarted. (Reference: 365163)
Resolution: The Common Management Agent's policy compilation process was updated to detect this error and retry the policy compilation during the next policy enforcement.
8. Issue: The Common Management Agent installation could fail to complete due to the JrMac process being reported as in use. (Reference: 390315)
Resolution: The Common Management Agent installation process was updated to rename the file in use and mark it to be deleted at the next reboot.
9. Issue:*The Common Management Agent sometimes failed during the policy enforcement process, resulting in the distribution of incomplete policies to managed products. Incomplete policies for Host Intrusion Prevention could prevent systems from accessing the network. (Reference: 400825, 403015)
Resolution:*The Common Management Agent was updated to record the ePolicy Orchestrator server Internet Protocol (IP) address, name, and communication port, and the Common Management Agent wake-up port.
10.Issue:*The update process of the Common Management Agent sometimes failed and the system was not updated to the latest DAT file. This issue was seen more frequently on servers running VMWare, but not exclusively. (Reference: 359975)
Resolution:*Access to the internal components of the Common Management Agent was broadened, allowing the update process greater access to these components.
11.Issue:*Systems receiving the Common Management Agent after an ePO server’s Internet Protocol (IP) address was changed could no longer contact the ePO server. This issue occurred with any version of ePolicy Orchestrator, and with Common Management Agent 3.6.0 Patch 2 or Patch 3. (Reference: 391641, 392465)
Resolution:*The Common Management Agent manifest for rebuilding deployment packages was updated to create correct deployment packages.
12.Issue:*When the Common Management Agent was running on Terminal Server 2003 systems, the UdaterUI (and McAfee icon) process was unnecessarily created for every logged-on user. (Reference: 402678)
Resolution:*The Common Management Agent UdaterUI process was updated to create only a single instance for each system.
13. Issue:*The Common Management Agent contained a security flaw that could allow an attacker to corrupt the memory of a system. Corruption of this memory might lead to remote code execution. (Reference:*398370)
Resolution:*The*Common Management Agent was updated to remove this security flaw.
14.Issue:*The Common Management Agent contained a security flaw that could allow an attacker to corrupt the memory of the system. Corruption of this memory could lead to a denial of service attach. (Reference: 402744)
Resolution:*The*Common Management Agent was updated*removing this security flaw..
In the readme file for installation of the patch 4 of the 3.9.0 agent, we can read for the step 2 of installation "Checking in a New NAP file
1. In the console tree under "ePolicy Orchestrator" | <SERVER>, select "Repository." 2. In the details pane under "AutoUpdate Tasks," click "Check in NAP." The "Software Repository Configuration" wizard appears. 3. Click "Next" to add new software to be managed. 4. Select the NAP file (CMA360.NAP) from the temporary folder you created in Step 1 of "Installing Common Management Agent 3.6.0 Patch 4 Steps." 5. Click "Yes" to overwrite the existing NAP file. 6. Click "OK" after the software repository configuration has completed. " I can't find the nap file in the zip archive of the patch 4.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.