Hi there.
It's me again
Downloaded and checked in Mcafee 4.6 with patch 3 (MA460P3WIN.ZIP) into our EPO 4.6 console.
Clients currently have version 4.6.0.2935.
If I go to EPO --- SYSTEM TREE --- Select 1 agent --- Actions --- Deploy Agents, Force Installation over existing version and magically watch what will happen in server task I recieve FAILED.
Is there any more user friendly message in new EPO beta version, because simply one word FAILED without any extra information is not quite helpful?
Well, the idea is how to achieve the upgrade from Mcafee Agent for Windows client version from 4.6.0.2935 to 3122? Any magical tricks?
p.s. - And another thing, is there only patch 3 available for download and not Mcafee agent with patch3 included ZIP file? I haven't find it on Mcafee My Product downloads... we are gold partner.
With best regards
Message was edited by: bostjanc on 12/19/12 2:27:08 PM GMT+01:00Solved! Go to Solution.
The two most common issues I can think of:
1.) NetBIOS ports not open which would not allow ePO to connect to the Admin$ share on the target. Windows Firewall turned on? etc...
2.) Credential using to push the agent was fat-fingered or did not have the necessary access rights on that system. Account needs to be a local administrator.
That said, even though it reports that the installed failed, you should be able to dive deeper to find out what error was. Providing that to us will allow us to get you a better answer.
Regards,
Mark
All the agent patch installers are full installers, so there's only the one package.
If the clients have already got agents on then you can use a deployment task to upgrade them - it's probably the easiest method.
HTH -
Joe
Joe thank you for your reply.
can you explain it to me why Deploy Agents / Force Installation over existing version does not work? I tought this is one of the approaches that should work.
with best regards,
The two most common issues I can think of:
1.) NetBIOS ports not open which would not allow ePO to connect to the Admin$ share on the target. Windows Firewall turned on? etc...
2.) Credential using to push the agent was fat-fingered or did not have the necessary access rights on that system. Account needs to be a local administrator.
That said, even though it reports that the installed failed, you should be able to dive deeper to find out what error was. Providing that to us will allow us to get you a better answer.
Regards,
Mark
I had a dog and BINGO! was his name.
Mark, as your were mentioning (2.) now I remember removing domain admins from my local group, since the collegues did some pranks on my pc.
Yep, that was the reason for Mcaffe agent not deploying. Thank you for the hint.
With best regards,
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: