Client always shows the System State as Inactive (MfeEpe.log: 0xEE000004 System is not active)
Last Modified: 2024-01-06 09:49: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.
Client always shows the System State as Inactive (MfeEpe.log: 0xEE000004 System is not active)
Technical Articles ID:
KB73848
Last Modified: 2024-01-06 09:49:30 Etc/GMT Environment
Drive Encryption (DE) 7.x For details of DE-supported environments, see KB79422 - Supported platforms for Drive Encryption 7.x. Problem 1Some systems fail to activate after installing DE.
Client side: On the client, the user sees the following in the Encryption System Status window, even though the encryption policy was activated in ePolicy Orchestrator (ePO):
ePO Console: The administrator sees the Client System Details for DE:
When an administrator clicks More, Disks the following message displays: Problem 2The
WARNING MfeEpeEsEncryptionInformationService ..\..\..\Src\EpeFsmHostErrorHandler.cpp: EPE_fsm_host_error_handler::handle: 71: Received service unavailable exception: The service MfeEpeEncryptionInformationServiceClient is currently unavailable ERROR MfeEpeGenEncryptionProviderPlugin ..\..\..\Src\EpeGenInitHandler.cpp: EPE_gen_init_handler::handle: 181: [0xEE040001] CauseThe deployment option to Run at every policy enforcement is enabled.
If you have many assigned users, it takes longer to synchronize the users with the ePO server. The next enforcement task starts before the synchronization finishes. This task cancels the previous task because it doesn't have enough time to complete. A policy enforcement interval of 10 minutes isn't long enough to process many assigned DE users.
Solution 1In your DE deployment task, take one of the following actions:
Affected ProductsLanguages:This article is available in the following languages: |
|