This content has been marked as final. Show 11 replies
Instead of deploying the engine try to check in a superdat and deploy it to one of these computers with an Update (Mcafee Agent).
This will overwrite DAT and engine, if it works you can extend the task to the other computers
Not too sure if the Superdat will help you. In my experience, the SuperDat only contains the 5300 engine which you are already using. The 5301 engine is an incremental engine update and I believe not part of the superdat.
This is a known problem with McAfee Agent 4.00.1421. To fix the problem download and install McAfee Agent 4.0 Hotfix 481806. This hotfix upgrades the agent to v220.127.116.114 .
I think I'll need a team of staff just to keep up with fixes for McAfee software sad
I have the same problem, please could you give me a link or more details about where I can download McAfee Agent 4.0 Hotfix 481806.
This issue is resolved in McAfee Agent 4.0 Hotfix 481806., which is currently available for download on the McAfee ServicePortal and McAfee Downloads site.
For products, Service Packs, Patches, hotfixes or documentation:
Visit the McAfee website (http://www.mcafee.com). For instructions, see KnowledgeBase document KB54808.
For downloading Patches only:
Visit the McAfee ServicePortal(https://mysupport.mcafee.com). For instructions, see KnowledgeBase document KB56057.
Previously, McAfee Agent 4.0 Hotfix 5 (MA400HF478043WIN.zip) resolved this issue. This installer change was also included in subsequently produced hotfixes.
Unfortunately we have run into another problem:
In approximately 50% of our clients, Agent v18.104.22.1681 will not successfully deploy the v22.214.171.1244 agent. The agent reports "Error occurred while downloading FramePkg.exe." sad We are forced to either manually download and install on the affected computers or remove them from EPO and add them in again as a new agent using Windows to push out the install.
Either way with hundreds of clients this is going to be a very time consuming process.
McAfee's quality control and testing of their products before release is abysmal.
Having the same issue as Kao "Error occurred while downloading FramePkg.exe." deplolying the v126.96.36.1994 agent.
Anyone found a resolution to deploy via ePO rather than from deployment via other an source?
What type of repository types are failing ?
They are distributed repositories (13 of) on Netware servers (UNC paths)