Click on the Category button to get more articles regarding that product.
Mcafee/Trellix EPO 5.10 SP1 Update 2, LDAP Sync Save Agent Settings FAILS/Stalls Bug
Do not add, change, or modify Organizational Units (OUs) in Active Directory where you sync via LDAP. You won’t be able to change the LDAP Sync settings in EPO 5.10 SP1 UPD.
We have just wasted a full morning on a bug in EPO 5.10 Service Pack 1 Update 2 because we thought it was related to some kind of SQL Server permission for our service_trellix_myuser permission on some Stored Procedure under SQL 2017 on SRV 2022. However, it looks like this is related to a bug. It does not work even if you run/connect to SQL with sa or domain\administrator.
We are really unhappy that the forums have been down since NOVEMBER 2023, and we stumble over such bugs. It may be related to Microsoft doing what they want for the Credentials SAVE bug here.
Here is what we talk about: We want to provide credentials for the automatic Agent Deployment for new clients we see in LDAP/Active Directory.
It keeps SAVING herfe forever…
Unable to save the Push Agent configuration under AD Synchronization in ePO
Technical Articles ID: KB96965
Last Modified: 2024-02-01 10:13:36 Etc/GMT
Environment
ePolicy Orchestrator (ePO) 5.10 SP1 Update 2
Problem
Log on to the ePO console and go to System Tree, Group Details, Synchronization type, Edit. You should have the ability to configure the following:
-
Push agents to new systems when they’re discovered
-
Select the option Configure Settings
If you make any changes to these sections and then select Save or Cancel, it doesn’t return to the previous page or the updates can’t be saved.
Cause
The function name for adding the event handler for the Save and Cancel button conflicts with another function, resulting in the buttons not working.
Solution
We investigated this issue and a Proof of Concept (POC) Build is currently available to resolve the issue. To obtain the POC Build, log on to the ServicePortal and create a Service Request. Include this article number in the Problem Description field.
We are really unhappy that the forums have been down since NOVEMBER 2023, and we stumble over such bugs. It may be related to Microsoft doing what they want for the Credentials SAVE bug here.
