/build/static/layout/Breadcrumb_cap_w.png

Miscellaneous Question


When does LDAP Sync occur?

03/08/2018 2052 views
I've been chasing my tail with this one and so has my colleague. When does Kace sync with LDAP (Specifically to apply LDAP labels)? It seems to be when the device checks in but we need it to ignore the device and look at AD really. Is this possible? 

Cheers all!
Answer Summary:
0 Comments   [ + ] Show comments

Comments


Answer Chosen by the Author

4
Per
https://support.quest.com/kace-systems-management-appliance/kb/200180/how-to-create-a-new-ldap-device-label

"NOTE: LDAP device labels DO NOT apply to the devices immediately.  A test, when used with an asterisk, will show the computers that should apply, but the label will NOT be fully generated until the KACE variable has been saved in the label and each device has completed inventory (checked-in with the K1000).  It will be necessary to wait until all desired devices have completed inventory and pick up the label before using it in a distribution."

It looks like is during the Check-in\Inventory phase.

That is for Device LDAP labels.

User LDAP labels are evaluated when a user logs in to the User\Admin Portal.

Check
https://support.quest.com/kace-systems-management-appliance/kb/131519/how-to-keep-ldap-filter-in-sync-with-k1000-appliance-user-records
Answered 03/08/2018 by: Channeler
Red Belt

  • I was thinking that was how it was going to work, that's a shame. Thanks, we spent ages looking for that very neatly named and rather obvious article, oops!

Don't be a Stranger!

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

Sign up! or login

Share

 
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