ePO fails to deploy agent

[Shaik_SharkFish]

Hi Team,

I followed below commands to deploy agent from epo.

steps:Menu | Systems | System Tree|Actions | Agent | Deploy Agents.

selected agent version 5.5.1.462 which is in Evalution branch.

checked :Force installation over existing version..

getting above error's..please explain how to deploy

[cdinet]

The epo server or agent handler server log will show what error you are getting.  For example, you will see push agent failed, err = 53 or some other error code.  You can use command prompt - net helpmsg 53, for example, to find out what that specific error code means.  There are many reasons for failure, so check kb56386 for environmental requirements to push agents.  Basically, from the epo server, you have to be able to get to the admin$ share of that client with the credentials you are using to push agent.  If you can't map a drive to that system's admin$ share, then neither can epo push an agent.

[Hawkmoon]

Hi Shaik_SharkFish,

Quick ask for you.
Does you client(s) conform/are set up as described here please?

Deploying the McAfee Agent

[denn · Accepted solution]

If you using only ePO without AH try to telnet from ePO servet to client with 445 port.

It should be open if you want to deploy MA from ePO.

[Shaik_SharkFish]

Port connectivity is open ,
sever already having older version of McAfee Agent 5.5.1.388 am trying to push 5.5.1.462
and i have AD admin access,is that okay to install.

[cdinet]

Yes, it is ok to install.  If the current agent is communicating fine, you might just want to set up a deployment task for the agent as a client task assignment rather than push agent - a client task doesn't need credentials or the environmental requirements that a push agent process needs.