When Active Directory synchronization fails, the server task log shows that ePO tries to connect to the wrong server
Last Modified: 2022-04-20 08:52:18 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.
When Active Directory synchronization fails, the server task log shows that ePO tries to connect to the wrong server
Technical Articles ID:
KB95533
Last Modified: 2022-04-20 08:52:18 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.10-CU 12 and earlier
Problem
An Active Directory synchronization task fails. The server task log details indicate that this failure occurs on a registered server that the sync point isn't configured to point to. You might also see a reference to a registered server that isn't an LDAP server. For example:
This log activity shows that ePO actually points to the correct server. A Wireshark capture also reveals that ePO actually tries to connect to a valid registered LDAP server. The log activity shown in the server task log shows inaccurate information. ePO doesn't try to connect to the wrong LDAP server. The registered server referenced in the Server Task log isn't the registered server that the Active Directory sync tries to connect to. The ePOApSvr log shows the LDAP server that ePO fails to connect to, and the reason for it. Cause
This issue is caused by the way in which the server task log identifies which registered server ePO connects to. NOTE: This issue is cosmetic, and displays incorrect information in the Server Task log. This issue doesn't cause ePO to point to the incorrect registered server. Solution
This issue is resolved in ePO 5.10.0 Update 13, which is available from either the Software Catalog or the Product Downloads site. NOTE: You need a valid Grant Number to access the update. To view all resolved issues, see KB90382 - ePolicy Orchestrator 5.10.x Known Issues. Affected ProductsLanguages:This article is available in the following languages: |
|