Replacing corrupted McAfee agent - 'install over' or 'remove/reinstall'

[Former Member]

Which is the better way to reinstall an agent that appears to be corrupted?

Install framepackage right over the current agent/?

Or, does the old agent need to be removed first, and then reinstalled?

PG

[Former Member]

We have great success using /agent=install /forceinstall

[Former Member]

Dear Hbss,

If you wants to reinstall the MA on a single machine kindly use this command for uninstallation

1)Type CMD fron run (make sure that u have admin rights)

2) Type cd  C:\program files\McAfee\Common Frameworks

3)run the command frminst /remove=agent and press enter

if you wants to reinstall more than one PC from ePO console kindly follow the procedure

1)log in in to the ePO console

2) select the PC's that u wants to reinstall the McAfee agent

3)then select the Actions TAB-Agent Option-Deploy agents

4)enable the check box " force installation over existing version"

5)type the credentials like domain name username and password then click ok

Hope this will helps u.....

[Former Member]

When i perform this action most of the times the action gets failed.

The situtaion is i have agent 5.0.4 installed on the machine, and i want tp update it to 5.5.1 which i have my repository, but its not getting updated even after doing the wake up agent.

[cdinet]

Is the deploy agent failing from epo side, or does epo show push was successful and it still fails on the client side?

[Former Member]

the ePO shows it failed.  Also if i use Run client task to update it fails.

[cdinet]

I see you posted the same question in another post.  You might be better off to start with a fresh post next time.  

There are environmental requirements for deploying an agent from epo.  See KB56386.  There are specific error codes and many reasons for the failure.  In the server log you would see an entry push agent failed to systemname, err=53 or some other random number.  

In command prompt, run this - net helpmsg 53 (or whatever error code it was).  That will return what the error code means.  1326 is bad password, 5 is access denied, 53 is network path not found.  That last one could be several things.  Firewall blocking it, system off, dns not resolving, admin$ share not accessible, etc.  So you will need to either do a little investigating on the cause of the failure, or open a ticket with McAfee for us to assist.

Things to test:

Can you access the admin$ share of the client from the epo server?  You must either be logged in with the deploy agent credentials, or attempt to map a drive using those credentials.  If you are able to do that, can you write to that directory?  If you can't get to the admin$ share and write to it, then neither can epo to push an agent.

[Former Member]

When i am try to access the admin share of the client machine it throws an error, we have full admin rights on all the environment machine, we are the local Admins as well.

Also please guide where can i check the error code, you just mention error 53

[cdinet · Accepted solution]

On the epo server in the install directory for epo, go to the db\logs folder and there is a server_servername.log file.  That is where you will see push agent failed message.  

If you can't access the admin$ share, then you need to check the KB I gave you to ensure the client has all the environmental requirements enabled - file and print sharing, remote registry, required services running, etc.

[Former Member]

Thanks man you are the saviour.

Agent is successfully installed, i had saved my password and remembered it, i checked the logs you advised and found it was password issue.

Issue is resolved :-). You solved my big problem although i was doing the silly mistake.