Using the 'noguid' command to prepare for an image does not remove the old Agent GUID
Last Modified: 2021-02-02 20:02:31 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
After December 1, 2024, please log in to the Thrive Portal for support, knowledge articles, tools, and downloads. For information about using the Thrive Portal, view the Trellix Thrive Portal User Guide.
Using the 'noguid' command to prepare for an image does not remove the old Agent GUID
Technical Articles ID:
KB94064
Last Modified: 2021-02-02 20:02:31 Etc/GMT Environment
McAfee Agent (MA) 5.7.1, 5.7.0, and 5.6.x Problem
When you run the Location of the Agent GUID can be found at: If you reboot the primary image, or bring up any new image, the old Agent GUID is retained in the location above. On the first agent-server communication interval (ASCI). The value changes, and is updated with the correct Agent GUID. Solution 1
This issue is resolved in McAfee Agent 5.7.2, which is available from either the ePO Software Manager, or the Product Downloads site. To view other known and resolved issues, see KB93773 - McAfee Agent 5.7.x Known Issues. NOTE: You need a valid Grant Number to access the update. Solution 2We investigated this issue and a Proof of Concept (POC) Build is currently available to resolve the issue. To obtain the POC Build, log on to the ServicePortal and create a Service Request. Include this article number in the Problem Description field.
Workaround
Manually delete the Agent GUID entry in the registry before saving the primary image. CAUTION: This article contains information about opening or modifying the registry.
Affected ProductsLanguages:This article is available in the following languages: |
|