--- title: "Identifying duplicate agent GUIDs ( ePO - On-prem )" slug: "identifying-duplicate-agent-guids-epo-on-prem" tags: ["Agent", "Product Usage"] updated: 2026-08-26T19:15:25Z published: 2026-08-26T19:15:25Z canonical: "docs.trellix.com/identifying-duplicate-agent-guids-epo-on-prem" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Identifying duplicate agent GUIDs ( ePO - On-prem ) When client systems with duplicate GUIDs attempt to communicate with an Agent Handler, they generate sequencing errors, which indicate a GUID problem. The **Managed Systems** query result type tracks this information about the sequence errors. - The number of sequence errors for each system in the **Managed Systems Sequence Errors** property. - The date and time of the last sequence error in the **Managed Systems Last Sequence Error** property. The tracked information is incorporated into one of the available predefined queries: - **Systems with High Sequence Errors** - **Systems with no Recent Sequence Errors** Two predefined tasks help manage GUID problems. - **Duplicate Agent GUID - remove systems with potentially duplicated GUIDs** This task deletes the systems that have many sequencing errors and classifies the agent GUID as problematic. As a result, the agent is forced to generate a new GUID. The threshold number of sequencing errors is set in the query **Systems with High Sequence Errors**. - **Duplicate Agent GUID - Clear error count** Sequencing errors can occur occasionally for inconsequential reasons. This task clears the count of sequencing errors in systems that have not had any recent sequencing errors. This cleanup task does not remove any problematic GUIDs. The threshold value for defining recent is set in the query **Systems with no Recent Sequence Errors**. :