I talked to Jamf support yesterday and we think we may have found why it doesn't work. Basically, in order to do the live LDAP lookup, an initial lookup needs to be performed so that an LDAP ID is populated. This normally shows up in the left bottom portion of the location tab.
The problem lies when information changes and doesn't match against LDAP, specifically (for us anyway) with the Department field. If I pull my information from LDAP and populate my Department, it will be populated as "11-70." (We use our profitCenter attribute in LDAP as Department.) Now, because I have "11-70" defined as a department in the JSS, it matches what LDAP provided and fills it in.
Here's the problem: Let's say I changed departments (precicely the thing I want live LDAP lookup to handle). If my department in the JSS and department on LDAP mismatch, I get a "no results found" when performing the lookup. Support was able to replicate it on their end and is taking it to Dev.
In reality, the JSS shoudn't care – AT ALL – what it has in its record beyond the LDAP ID. I want everything pulled from LDAP, every time. Name, position, telephone number, email…. Everything. There shouldn't be matches.
So, support's aware and is working on it.
j
--
Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436
