Point product version information is not correctly updated after you apply ePO 5.10 Update 5
Last Modified: 2023-03-27 16:38:44 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.
As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
Point product version information is not correctly updated after you apply ePO 5.10 Update 5
Technical Articles ID:
KB92203
Last Modified: 2023-03-27 16:38:44 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.10 Update 5
Problem
After you apply ePO 5.10 Update 5, the product version property for Example sequence of events:
System Change
You applied ePO 5.10 Update 5.
Solution
This issue is resolved in ePO 5.10.0 Update 6, which is available from the Product Downloads site. NOTE: You need a valid Grant Number to access the update. To view other known and resolved issues, see KB90382 - ePolicy Orchestrator 5.10.x Known Issues. IMPORTANT The above resolution only prevents the issue from happening in the future. Systems that currently show incorrect versions in ePO need to send their full properties to ePO at least once. Send full properties can be achieved using either of the following methods:
WorkaroundThis issue is intermittent. The next time the McAfee Agent submits its version information, it might update correctly. But, in normal agent-to-server communications, the agent does not resubmit its version information because it has not changed since the last communication.
As a workaround, you can schedule a client task on the affected clients to run a wakeup call and submit their full properties:
NOTE: If you incur problems with the above workaround, contact Trellix for assistance. IMPORTANT: The following files are required for Technical Support:
To contact Technical Support, go to the Create a Service Request page and log on to the ServicePortal.
Affected ProductsLanguages:This article is available in the following languages: |
|