This is still happening with version 5.02.132, 5.02.188 and 5.02.333 Agents.
Can anyone confirm that they are seeing the same with query "Engine Version Deployment" ?
For info we are running ePO v5.3 build 188.
Maybe I am missing an extension?
Thanks for looking
Many issues with agent 5.x: agent not communicating, or just not running tasks or policy not being up to date.
Little know fact: the agent is dependent on crypto and power services, they must be up and running and set to automatic (not delayed)
I rolled back to 4.8 and I'm waiting for agent 5.03
This whole upgrade path with Agent 5.x is a pain. Have been doing some testing but have yet to fully deploy these 5.x agents. What you guys are finding is making me rethink about deploying 220.127.116.113. We have about 200+ systems using agent 18.104.22.168 due to Windows 10. Had issues with 22.214.171.1248 with Windows 10 and was told by support to use agent 5.x. The majority of our systems, over 1500, are still on Agent 126.96.36.1998. At least VSE 8.8i Patch 7 installs with the 4.8 agent.
I know that McAfee was telling people to upgrade to 188.8.131.523 to close a security vulnerability. What I have read is that you can have Agent 184.108.40.2068 and install Patch 7 this should close this security vulnerability. I hope that info about this vulnerability is correct.
Our biggest issue with Agent 5.x is with Drive Encryption as it won't enforce policies. Have an open case with McAfee with that issue. Back in Nov, was told to wait for Agent 5.0.3 also.
Thanks for your input,
I'll assume this will be fixed in a later engine update.
Its not really an issue, just a cosmetic problem.