How to stop the Agent Handler service before running the Cumulative Update on ePolicy Orchestrator
Last Modified: 2023-03-17 10:05:07 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.
How to stop the Agent Handler service before running the Cumulative Update on ePolicy Orchestrator
Technical Articles ID:
KB96397
Last Modified: 2023-03-17 10:05:07 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.10.x
Summary
This article describes how to stop the Agent Handler service before running the Cumulative Update on ePO. Perform either of the following options to check the number of Agent Handlers reporting to ePO: Option 1:
The Agent Handler name is CLIENT (it's reflected in the console). It's recommended to stop the services of the Agent Handler, because the active sessions to the database for multiple activities from the Agent Handler might interrupt the running of scripts that execute during the CU update. When the existing session is active, it doesn't allow the Cumulative Update from ePO to modify the SQL scripts as expected. So, you must make sure that all Agent Handler services need to stop before running the Cumulative Update on ePO. Perform the steps below to stop the services on the Agent Hander system:
Affected ProductsLanguages:This article is available in the following languages: |
|