Agent 2.0 and 3 installed on client

[SlurpeeGuy]

I have users that show both the old 2.0 agent and the new 3.0 Framework agent. Any downside to having them both on the client? If i wanted to remove the 2.0 agent how would I do so? TIA

 

[ReallyTallCupboards]

We had this a while ago after upgrading from EPO 2.5 to 3.0.
Although most clients appeared to run both agents with no issues, some started with both agents running at 100% CPU.
This was cured by removing the old agent (which in our case was installed in c:\epoagent, seperate from the new location in prog files) using the following command line:

c:\epoagent\frminst.exe /REMOVE=AGENT

 

[AVChap]

Theoretically, that would not be possible (running both versions of the agent) as the agent installer would automatically look for a previous version, uninstall it if found, then install the new version.

Yes, the old directories might still be there, but there will only be one version of the agent running on the machine.

BTW, no need to remove the old version if you agree with this idea.

AVChap

“I have not failed 700 times. I have not failed once.
I have succeeded in proving that those 700 ways will not work.
When I have eliminated the ways that will not work,
I will find the way that will work.”
--Thomas Edison

 

[SlurpeeGuy]

I found my fix for this by re-pushing the 3.o agent FROM the Epo server. Clients are now able to receive tasks now and no longer report that they have 2.o agent installed.