STOP McAfee pushing AGent to select clients?

[User20107492]

We are doing a clean standalone install of ePO 5.10. Our current environment ePO 5.3.2 must continue to serve the estate while we set up the new one. What is the best way to get our old install to stop automatically pushing its agent to a select few clients so I can push the agent to them manually from the NEW ePO? I basically want the current ePO to ignore these clients totally and not pick them up on a scan or try to push anything to them.... Thank you

[AdithyanT]

Hi @User20107492,

Thank you for your post. May I know how you have exactly configured automatic pushing of Agents for newly added systems from your old ePO?

Also, You can always force install McAfee agent from new Server even if you have an existing Agent installed and reporting to old ePO and it should work just fine.

[User20107492]

Hi, yes I can force an new agent install over the old one but the old one still serves up the products and policies it has and then eventually the agent reverts to the old one again anyway. Even if I remove the client from ePO and remove all products it reappears automatically and has the agent and therefore all the products and policies too.

I cannot find a client task, a server task, a policy that relates to installing the agent apart from when I manually add a client or I select and push agent... where will I find the auto setting?

[LKS · Accepted solution]

Hi User20107492,

As @AdithyanT  mentioned you can do "Force agent install from ePO". However you have to stop Pushing Agent from old EPO in order to avoid new client machine picking Agent from old EPO. Check if you have any server task configured to deploy Agent. If you have AD sync configured with "Push agents to new systems when they are discovered",  please disable it.

Was my reply helpful?

If you find this post useful, please give it a Kudos! Also, please don't forget to select "Accept as a Solution" if this reply resolves your query!

[User20107492]

This could be it let me have a look as I know we do adsync the system tree.

[User20107492]

Thank you. I have now found the Push Agent install in the group sync. I did add the clients into the excluded section here but it clearly didn't work so now i'll stop the push or maybe the 'force install if not controlled by this server'

[AdithyanT]

Hi @User20107492,

Thank you for your update and letting us and other community members know what helped you. Kudos to your for the same!

[User20107492]

Unfortunately I still struggle on.

On both groups in the system tree that adsync picks up these particular clients I have unchecked the box 'Push agents to new systems when they are discovered' yet everytime ADsync runs the client reverts back to the old ePO handler and therefore receives the policies and tasks to install all the products again!

What else could be pushing the agent? I have no client tasks for it assigned and no product deployment set.

I have also looked at lost and found in case it was installed there first before being sorted (by IP range) but there is no group criteria.

ANy thoughts?

[AdithyanT]

Hi @User20107492

If ePO is not doing the "deployment of old McAfee Agent", can you confirm if you have a logon script or any other deployment solution that is doing this?

[AdithyanT]

@User20107492,

Just trying to get to the bottom of this. Are you sure that the old agent is actually getting installed on the machine? Can you confirm if you find new Agent installation logs in your endpoint?

Locating the install logs:

• %TEMP%\McAfeeLogs, if the McAfee Agent is installed or upgraded manually.
• C:\Windows\Temp\McAfeeLogs, if McAfee Agent is installed using push or deployment task on McAfee ePO.

Log file to look for: Frminst_<hostname>.log

Kindly please check and confirm the presence of this file.