I posted a similar question to this in another posting, so some of you may have already seen it.
Background: I have a Windows 10 PC (build 1607, Anniversary Update) with McAfee Agent 4.8 patch 3 (18.104.22.1688) and VirusScan 8.8 patch 8, which according to this KB McAfee Corporate KB - REDIRECTED - McAfee Agent support for Windows 10 KB84916 are all supported on this build of Win 10.
Issue: Existing product deployment and product update tasks (such as DAT and engine updates) assigned to my PC aren't being sent to my PC. I don't see them as managed tasks within the VirusScan console. However, if I create brand new deployment or brand new update tasks they are seen. Note, editing an existing task or assignment does not help. I don't have this issue with Win 7, all new installs get all of the existing deployment and update tasks.
Note, existing managed on demand scan scan tasks work fine. Deployment and Update tasks are McAfee Agent, and On Demand Scan tasks are VirusScan. So maybe this is an issue with tasks created with the old McAfee Agent extension?
Has anyone noticed this before? I guess the workaround would be to re-create all deployment and update tasks.
Known issue with 4.8 Patch 3 (22.214.171.1248) & WIN 10; open a SR, request 4.8.0 Patch 3 HF6 (126.96.36.1993). You may need to send them MER Logs OR IF your WIN10 are critical infrastructure systems, not able to pull MER logs due to the infrastrucure 😉 tell them so and they MAY send you the HF6 without the MER Logs.
McAfee Agent 4.8.0 Patch 3 HF6 (RTS) addresses KB86502 & KB86509
KB86502: McAfee Agent incorrectly reports the number of installed CPUs on systems with large numbers of physical or virtual CPUs: McAfee Corporate KB - McAfee Agent incorrectly reports the number of installed CPUs on systems with ... Disregard the solution: This issue does not occur with MA 5.0.x. ... Unless you want to go to MA 5.ohhhhh
KB86509: Agent communication and policy enforcement failure occurs on McAfee Agent 4.8 after installing to Windows 10 when VirusScan Enterprise 8.8 Patch 6 is already installed: McAfee Corporate KB - Agent communication and policy enforcement failure occurs on McAfee Agent 4.8 ... Disregard the solution: This issue does not occur with MA 5.0.x. ... Unless you want to go to MA 5.ohhhhh
188.8.131.523/WIN 10 does correct the communication/policy issue while still providing all the functionality and features of the 4.8 agent - Not a big fan of the 5.ohhhhh agent ... it's a step backwards.
If after duplicating a McAfee default policy (read only), making some changes, sending it to a single machine, and the policy arrives well to the final client, so it means the communication is established, either MA and VSE are working as they should.
furthermore, it means that during the last installation of the extension those old policies and tasks are now corrupt due to incorrect migrating process while ePO was installing the newest extension, so those policies/tasks do not have backwards compatibility any longer, and from here my best recommendation is to recreate them from the scratch.