the way to delete duplicate guid for agent auto

[Soixam24]

Dear everyone,

Hello McAfee support,

I have many linux and windows system duplicate guid, now I want delete guid on all this system, does anyone have a way to execute the command automatically on all machines, or do i have to access each machine to run the noguid command?

Thank you so much.

[aguevara]

i guess this is part of your post from yesterday 🙂 

https://community.mcafee.com/t5/ePolicy-Orchestrator-ePO/How-to-show-Agent-GUID-on-linux-system/m-p/...

the article I shared there shows a way how you can black list the GUID from ePO and delete the system, once the Agents attempt a new communication to the server then it will create a whole new GUID and reappear into the ePO system tree

Regards

Alejandro

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

[Soixam24]

Thank you so much, it's me post yesterday. 

[Dwee]

can you share with me ?i can't find your post in those link, and i can't find working kb related to reset/delete agent GUID, (linux and windows)

[cdinet]

If you are getting duplicate guids due to your image having the agent, you need to fix your image first so issue doesn't reoccur.  See https://docs.trellix.com/bundle/agent-5.7.x-installation-guide/page/GUID-BB07DD02-3A09-450C-8A74-81A...

For existing systems with duplicate guid, follow these steps.

https://docs.trellix.com/bundle/agent-5.7.x-product-guide/page/GUID-074965B8-6ECD-4925-9086-455010B2...

[Dwee]

Hi CDINET,

I'm a bit confused on which action do i need to choose from these points:

A. example what is High Sequence errors ?

B. if we clear Agent GUID Sequence Error Count what the results ? or Move Agent GUID to Duplicate List and Delete Systems ?

My condition /Status : there's duplicate system/client (same name but sometime have different ip address) with different Agent GUID (checked via system tree columns) but have different last comm and Amcore version (only one that have status amcore up to date),

[cdinet]

First a little background on what happens when systems have the same agent guid.

Agent 1 checks in and sends a sequence number that increments with each asci (agent-server communication).

Agent 2 checks in and epo matches the system with the agent guid, but agent 2 sends in its own sequence number that doesn't match what epo would be expecting from what agent 1 sent in.  So the communication is rejected.

You first have to run the task then to move the systems with high sequence errors to duplicate list and let epo then delete that system.  When that happens, at next asci when agent 2 checks in with wrong sequence number, epo sends it a command to regenerate its agent guid so it will no longer be duplicate.

At that point then, after agent 2 regenerates its guid, it checks in fine then with no sequence errors.

Then you have to run the task to clear the high sequence count so that the previous systems don't get deleted again.