After checking in a new package, clients are unexpectedly upgraded even when the client Deployment task is blank
Last Modified: 2023-08-14 05:59:30 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.
After checking in a new package, clients are unexpectedly upgraded even when the client Deployment task is blank
Technical Articles ID:
KB81100
Last Modified: 2023-08-14 05:59:30 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.10.x Trellix Agent (TA) 5.x All Point Products Problem
After you upgrade point product extensions to the latest version via the ePO console and check in the client software, the client deployment task values go blank for products to deploy.
Cause
If you check in a new package to ePO into a branch that contains a previous version of the product, any associated client tasks are blanked out; this prevents the task from upgrading the client by checking in new software. But, to update the task on the client, the client must communicate with ePO. If the client hasn't yet communicated with ePO, it downloads the product version that exists in the repository, and if it's a higher version, that new version is installed. This can also occur if the task is scheduled to run immediately. Since there's a change to the task, the client runs it again. SolutionBefore you check in any new version of a product, disable any client deployment tasks related to that product. Give the clients time to avail that change, and then you can check in the new version. After checking in the new version, edit the task to reflect the new version and enable it again as desired. It's always advisable to test the new version before you deploy it to the whole environment.
Affected ProductsLanguages:This article is available in the following languages: |
|