LDAP Label not populating Manual Label
Im not sure that if im doing this correctly, but I couldn't find this elsewhere in the forums.
I am able to see entities in testing:
BaseDN: DC=mydomain,DC=local
Advanced: (&(samaccountname=KBOX_COMPUTER_NAME)(memberof=CN=GPO.ServerKaceAgent,OU=Security Groups,DC=mydomain,DC=local))
results:
Testing LDAP Label Settings...
Testing "Standard SVR Baseline" connection to: ldaps://mydomain.local on Port: 636
OK: Connection Successful.
OK: Setting Protocol Version 3 Successful.
OK: Setting LDAP REFERRALS Option 0 Successful.
OK: Search Bind using LDAP supplied credentials Successful.
Applying search filter [(&(samaccountname=*)(memberof=CN=GPO.ServerKaceAgent,OU=Security Groups,DC=mydomain,DC=local))]
OK:
LDAP search (with filter
[(&(samaccountname=*)(memberof=CN=GPO.ServerKaceAgent,OU=Security
Groups,DC=mydomain,DC=local))]) Successful.
OK: LDAP Search successful with 3 entries found.
OK: LDAP Test Successful. Closing connection.
However, the associated manual label is never populated, even after forcing agent check in on those three servers.
im not sure exactly what im doing wrong here? Edit: i should also note that the servers show up in the devices inventory properly.
-
I'm not sure I would expect the content of the manual label to change even though the LDAP label sit on top, does the LDAP label itself change? Also check that the search base DN is working - Hobbsy 4 years ago
-
the Manual label is just a container for the LDAP label to return results into. My issue was that samaccountname is used with user accounts, but name= is used with computer accounts (in this context) - Notthatguy 4 years ago
-
I spoke with Kace support on this, as it turns out, samaccountname= should be name= instead - Notthatguy 4 years ago
