Disabled Active Directory computer objects are not imported into ePolicy Orchestrator
Last Modified: 2022-03-02 21:50:05 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.
Disabled Active Directory computer objects are not imported into ePolicy Orchestrator
Technical Articles ID:
KB79470
Last Modified: 2022-03-02 21:50:05 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.x
Problem
An Active Directory (AD) Synchronization task does not import disabled AD computer objects to the ePO System Tree. A similar action happens if you already imported these computer objects to ePO, and you disable the objects in AD. If you configure the AD Synchronization task with the following option, the task deletes these objects from the System Tree the next time it runs: Solution
This behavior is expected. The LDAP query ePO uses to retrieve AD computer objects was changed to ignore disabled computer objects. Because our LDAP query does not retrieve these objects, they are invisible to ePO. So, these objects are treated no differently than a non-existent or deleted computer object. Affected ProductsLanguages:This article is available in the following languages: |
|