KACE Product Support

I don't know of any negative impact. If it is incorrectly configured, you may have to login with the built-in admin account locally to modify the LDAP settings.

Misconfiguration can be annoying, but no negative impact per say. Make sure you remove any LDAP servers in the authentication list that aren't valid for your environment; e.g.- modify or delete the templates that say kace.com in them ;)

We use LDAP from AD with KBOX for a daily dump of all the users. Then if a service desk ticket is created by a staff member by email or the web, the ticket gets filled in with their location, title and phone number. Very handy.

We tried using LDAP for identifying computers by their OU and it was working fine but the network engineers were seeing so many log entries on the AD server that we had to stop. All 10,000 computers were logging entries for looking up the AD computer OU they belonged to and they would each try the 30 different choices at every check-in. The logs on the AD server become so cumbersome it was difficult to search for other events! We settled on a naming convention (name begins with <site abbreviation>) to standardize at all sites instead.

Beautiful...Thanks!

Good answers above and one tip I can suggest is if you aren't going to use the default servers, Admin, Read Only Admin and Users delete them and add your own. If you leave them there and add a 4th you will go through all the top ones first before getting to your actual configured one. This won't cause anything more then a long delay in logging in but can get annoying after time.