KACE Product Support Question

LDAP Labels assigned incorrect users

09/24/2014 4065 views
Setup: K1000 v6 with the LDAP hotfix installed.

Disclaimer: I've never used the LDAP labels before, so I could just be misunderstanding something basic. I've imported the labels from LDAP and would like to begin utilizing them. By following the guide, I came up with the following setup:

Base DN: DC=random,DC=company,DC=com

Search Filter: (&(samaccountname=KBOX_USER)(objectcategory=user)(memberof=CN=Group Name,OU=Level 2,OU=Level 1,DC=random,DC=company,DC=com))

Label Attribute and Label Prefix are blank.

When I click the test button, the search succeeds with 10 entries found, as it should. However, once I run a manual user import to apply this label it gets applied to nearly 600 of my 2000 users. What am I missing?
Answer Summary:
You need to change KBOX_USER to KBOX_USER_NAME.
0 Comments   [ + ] Show comments


All Answers

You need to change KBOX_USER to KBOX_USER_NAME. It's an inconsistency in KACE that affects the LDAP labels. 
Answered 09/24/2014 by: h2opolo25
Red Belt

  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.
  • But if I change it to KBOX_USER_NAME I get 0 entries found. The results show that that part of the search filter gets translated to (samaccountname=*_NAME).
    • That is correct, but when it actually does the import to labels it will do it correctly. I guess that's another "bug" with it.
      • KACE logic hurts my brain sometimes, but it worked! Thank you!

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ