Loading...

Knowledge Center


McAfee Client Proxy 2.x Known Issues
Technical Articles ID:   KB83131
Last Modified:  10/8/2019
Rated:


Environment

McAfee Client Proxy (MCP) 2.x

Summary

Recent updates to this article
Date Update
October 8, 2019 Added 2.5.1 Release Notes link.
August 15, 2019 Modified MCP-2310 and MCP-2313 in the Non-critical known issues section for clarity.
August 13, 2019 Added MCP 2.5.0 information.
Added MCP-2310 and MCP-2313 to the Non-critical known issues section.
July 29, 2019 Removed links to unpublished 2.1.x Release Notes.
May 14, 2019 Added MCP 2.4.0 information.
 
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.


Product release information
MCP Version General Availability (GA) Release Notes
2.5.1 October 8, 2019 Release Notes
2.5.0 August 13, 2019 PD28454
2.4.0 May 14, 2019 PD28309
2.3.6 February 12, 2019 PD28215
2.3.5 October 2, 2018 PD28009
2.3.4 Update 1
(Build 2.3.4.161)
August 7, 2018 PD27902
2.3.4 April 24, 2018 PD27673
2.3.3 January 30, 2018 PD27496
2.3.2 November 13, 2017 PD27318
2.3.1 April 6, 2017 PD27006
2.3.0 December 16, 2016 PD26834
2.2.1 December 1, 2016 PD26845
2.2.0 August 3, 2016 PD26630

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.

Documented known issues

CRITICAL:
Reference Number Related Article Found in MCP Version Resolved in MCP Version Issue Description
1245566   2.3.4.161 2.3.6 Issue: ePolicy Orchestrator (ePO) 5.10 introduced a new feature for policy and client task change approvals. The MCP ePO extension does not support this feature.

1187004
  2.3.1 2.3.4 Issue: You install MCP on Windows 10, and then upgrade Windows 10 to R2. If you then uninstall MCP, the removal fails.

MCP uninstallation fails because the McAfeeLogs folder is missing from c:\windows\temp; it was removed as part of the upgrade.

Workaround: Create the folder McAfeeLogs in c:\windows\temp and uninstall MCP.
1186970   2.3.1 2.3.4 Issue: MCP alone is not supported with MA 5.0.5. If the client does not have VSCore installed and you install MCP 2.3.0.288, the MCPService fails to start.
1153407 KB87658 2.2.0 Host IPS 8.0 Patch 8 Hotfix 1153407 or Host IPS 8.0 Patch 8 Issue: When you install any McAfee product that includes SysCore 15.5 (such as MCP 2.2.0), it breaks the trust in Host Intrusion Prevention (Host IPS) 8.0 Patches 5–7.

Workaround: To avoid the issue, upgrade to Host IPS 8.0 Patch 8 before installing MCP 2.2.0 or later. See the related article for more information.


Non-critical:
Reference Number Related Article Found MCP Version Resolved MCP Version Issue Description
MCP-2313   2.5.0   Issue: After you enter the release code in bypass windows, the bypass windows do not automatically refresh (Mac Only).
 
Workaround: To manually refresh the bypass window, select another option from the Console menu, and then click Client Proxy to return to the window.
MCP-2310   2.5.0   Issue: When the UDP block flag is enabled, all IPv4 traffic sent to UDP ports 80 and 443 is blocked.
1217617   2.3.2 2.3.3 Issue: You configure the ePO Product Deployment task to run at a regular interval.
The task successfully downloads and installs MCP. But, when the task runs, it downloads and runs MCPInstallerx64.exe.
The installer detects that MCP is already installed and exits. The download of this file must not take place.

Solution: Resolved in 2.3.3.
1180352   2.3.1   Issue: Multiple ETL files are generated in the MCP log folder.
Multiple ETL files are generated with MCP continuous ETl in the log folder %Programdata%McAfee/MCP/logs on Windows 10 RS2.
1109569   2.1.0 2.1.2 Issue: The Disable McAfee Client Proxy pop-up window does not display on Windows 7 and Windows Vista operating systems.

Workaround: In the ePO policy Bypass List, bypass the following options and push the policy to endpoints: domain names, network addresses, network ports, and processes.

Resolution: This issue is resolved in MCP 2.1.2.
1026039   2.0.0   Issue: The web proxy server, for example Web Gateway, configuration in the MCP policy is incorrect, and is set to redirect traffic to a non-HTTP port on the web proxy server. If the web proxy server port holds the TCP connection for a long time, the MCP process for Mac OS X (mcpd) hangs during a connectivity status check. The process hangs until the web proxy server releases the connection.

Workaround: Deploy a new policy with the correct configuration and restart the computer.
1005447   2.0.0   Issue: Cisco AnyConnect VPN connections fail with MCP running.

Workaround: Add the VPN processes to the bypass list in the policy. Or, add the network address or addresses of the VPN servers to the bypass list in the MCP policy. For example, for Cisco AnyConnect VPN, add the following processes to the bypass list:
  • Cisco AnyConnect
  • vpnagentd
  • cscan
  • vpndownloader

Rate this document

Glossary of Technical Terms


 Highlight Glossary Terms

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