Client always shows the System State as Inactive (when the Drive Encryption Agent service isn't processing requests)
Last Modified: 2024-01-06 08:20:42 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.
Client always shows the System State as Inactive (when the Drive Encryption Agent service isn't processing requests)
Technical Articles ID:
KB82018
Last Modified: 2024-01-06 08:20:42 Etc/GMT EnvironmentDrive Encryption (DE) 7.2.x, 7.1.x
For details of DE 7.x supported environments, see KB79422 - Supported platforms for Drive Encryption 7.x. ProblemA small number of systems fail to activate after successfully installing DE.
The logs show that the process is stuck at creating events for Local Domain Users. Sending an Agent Wakeup call doesn't start the encryption process. On the client You see the following on the client in the Endpoint Encryption System Status window, even though the encryption policy is activated in ePolicy Orchestrator (ePO):
On the ePO console The administrator sees the Client System Details for DE as follows:
If you click More, Disks, you see the following message: CauseOne or both of the following services on the client are in a state that's not processing the requests to initiate the encryption process required to activate the client:
Solution 1On the client, restart both services and enforce policies via the Agent Monitor interface.
Solution 2If the previous solution doesn't resolve this issue, search the Knowledge Base using the following string (including the double quotation marks) to locate other content covering this issue:
Affected ProductsLanguages:This article is available in the following languages: |
|