No ePolicy Orchestrator detected (when running Pre-Installation Auditor)
Last Modified: 2023-07-11 07:06:21 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.
No ePolicy Orchestrator detected (when running Pre-Installation Auditor)
Technical Articles ID:
KB94683
Last Modified: 2023-07-11 07:06:21 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.10.x, 5.9.x Pre-Installation Auditor (PIA) (standalone version) Problem
When you attempt to run the standalone version of PIA on an existing ePO server, you see the message below. The message displays on the initial dialog box even though ePO is installed and working: The PIA NOTE: The Cause
This registry key below is missing: The key contains the values listed below, which the PIA tool is looking for when it's executed:
Solution
Repairs to the registry might be needed if any of the following apply:
Option 1 - Restore from a backup. If the above-mentioned registry keys are missing, it's conceivable that other keys could also be missing. Thus, the integrity of the ePO server can also be compromised. It might be necessary to restore the ePO server from a known good backup. Related article: KB52126 - How to back up and restore the ePolicy Orchestrator database using SQL Server Management Studio. Option 2 - Replace the missing keys. If only the above-mentioned registry keys are missing, you can resolve the issue by exporting the registry keys from a known good ePO server. Then, import them on the problem server. IMPORTANT: You must export the keys from an ePO server that has the same ePO version and build. Affected ProductsLanguages:This article is available in the following languages: |
|